magnusi
/
stavebniny
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
23 Commits
1 Branch
0 Tags
150 KiB
HTML 52.8%
CSS 45.8%
Rust 1.4%
 
 
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1439b770a5'
${ noResults }
Go to file
DavidOConnor 1439b770a5 Updated version 6 years ago
pkg Modified gitignore to preserver pkg directory 6 years ago
src Updated for v0.2.5 release 6 years ago
.gitignore Updated for update func taking Model, and removed nightly instructions 6 years ago
Cargo.toml Updated version 6 years ago
README.md Changes in readme to reflect improved build script 6 years ago
build.ps1 Changes in readme to reflect improved build script 6 years ago
build.sh Changes in readme to reflect improved build script 6 years ago
index.html Updated for v0.2.5 release 6 years ago
serve.py Updated for v0.2.5 release 6 years ago

README.md

Seed Quickstart

To get started:

  • Clone this repo

  • If you don't have Rust and wasm-bindgen installed, Download it, and run the following commands:

rustup update

rustup target add wasm32-unknown-unknown

cargo install wasm-bindgen-cli

If you run into errors while installing wasm-bindgen-cli, you may need to install a C++ build chain. On linux, run sudo apt install build-essential. On Windows, download and install Visual Studio 2017; when asked in the installer, include the C++ workload.

  • Run build.sh or build.ps1, then then start a dev server that supports WASM. For example, with Python installed, run python serve.py. (Linux users may need to run python3 serve.py.)

If you run into permission errors on build.sh, try this command to allow executing the file:chmod +x build.sh. If you run into persmission errors on build.ps1, open Powershell as an administrator, and enter this command: Set-ExecutionPolicy RemoteSigned.

Once you rename the crate in Cargo.toml (The name field under [Package]), make the following change:

  • Replace appname with your new name in either build.sh, or build.ps1, depending on your operating system.