diff --git a/dev/404.html b/dev/404.html index 5c33236..fb70c89 100644 --- a/dev/404.html +++ b/dev/404.html @@ -1 +1 @@ -
Before building your application, you must configure your project at the very least.
After you have done that, your application can be built using a local copy of this repository or via installation with Cargo.
The recommended method of downloading the repository is via the source
asset archives attached to each release.
The latest release can always be downloaded at the following URLs:
Specific releases may be downloaded at the following URLs, replacing X.Y.Z
with the desired version:
After unpacking the repository, enter the directory and run:
cargo build --release
The executable will be located at target/release/pyapp.exe
if on Windows or target/release/pyapp
otherwise. If a particular target has been set (or when cross compiling since one will always be set), then the release
directory will be nested one level deeper under target/<TARGET>
.
Select the directory in which to build the executable with the --root
option and run:
cargo install pyapp --force --root <DIR>
-
The executable will be located at <DIR>/bin/pyapp.exe
if on Windows or <DIR>/bin/pyapp
otherwise.
Specific versions may be chosen with the --version
flag.
Note: If you want to cross compile, this method of building is currently unsupported.
Configuration for cross is validated by CI to ensure all known environment variable options are passed through to the containers.
When embedding the project or the distribution using a local path, you must use the local repository way of building and ensure that the configured files to embed reside within the repository and the options refer to relative paths.
Some targets like powerpc64le-unknown-linux-gnu
need extra Cargo configuration to build properly. If there exists a file named .cargo/config_<TARGET>.toml
, then you will need to build using the local repository way and rename that file to .cargo/config.toml
before builds.
The executable will be located at <DIR>/bin/pyapp.exe
if on Windows or <DIR>/bin/pyapp
otherwise.
Specific versions may be chosen with the --version
flag.
Note: If you want to cross compile, this method of building is currently unsupported.
Configuration for cross is validated by CI to ensure all known environment variable options are passed through to the containers.
When embedding the project or the distribution using a local path, you must use the local repository way of building and ensure that the configured files to embed reside within the repository and the options refer to relative paths.
Some targets like powerpc64le-unknown-linux-gnu
need extra Cargo configuration to build properly. If there exists a file named .cargo/config_<TARGET>.toml
, then you will need to build using the local repository way and rename that file to .cargo/config.toml
before builds.