fork/Graphite
1
0
Fork 0
mirror of https://github.com/GraphiteEditor/Graphite.git synced 2026-10-01 22:38:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update website with improved student project details

Browse Source
This commit is contained in:
Keavon Chambers
2025-02-11 17:18:57 -08:00
parent f410efb8a8
commit 1700c3a650
7 changed files with 74 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/content/volunteer/guide/project-setup/_index.md
-4
View File
@@ -26,10 +26,8 @@ cargo install -f wasm-bindgen-cli@0.2.99
Regarding the last one: you'll likely get faster build times if you manually install that specific version of `wasm-bindgen-cli`. It is supposed to be installed automatically but a version mismatch causes it to reinstall every single recompilation. It may need to be manually updated periodically to match the version of the `wasm-bindgen` dependency in [`Cargo.toml`](https://github.com/GraphiteEditor/Graphite/blob/master/Cargo.toml).
<br />
<details>
<summary>Linux users: click here</summary>
<br />
On Linux, you likely need to install this set of additional packages which are required by Tauri, even if you're just building the web app:
@@ -70,10 +68,8 @@ This spins up the dev server at <http://localhost:8080> with a file watcher that
This method compiles Graphite code in debug mode which includes debug symbols for viewing function names in stack traces. But be aware, it runs slower and the Wasm binary is much larger. Having your browser's developer tools open will also significantly impact performance in both debug and release builds, so it's best to close that when not in use.
<br />
<details>
<summary>Production build instructions: click here</summary>
<br />
You'll rarely need to compile your own production builds because our CI/CD system takes care of deployments. However, you can compile a production build with full optimizations by first installing the additional `cargo-about` dev dependency: