Incorrect Build Instructions

[briangithex]

According to https://docs.velopack.io/contributing/compiling the correct way to build on Windows Release mode is as follows:

On Windows:

git clone https://github.com/velopack/velopack.git
cd velopack/src/Rust
cargo build --release --features windows
copy {path_to_osx_update} target/release/updatemac
dotnet build -c Release /p:PackRustAssets=true

copy {path_to_osx_update} target/release/updatemac is confusing (and no such step is included in the OSX build instructions). As a windows user, I'm not clear what {path_to_osx_update} even means. Is the documentation asking us to build the OSX version before building the windows version?

Of course, it's also possible this is just a documentation bug, rather than a clarity issue.

[caesay]

The compiling docs are out of date. You can build locally for dev purposes - I think all you'd need to do is cargo build and then dotnet build and you should have dev binaries working for everything on that specific OS. You can also review the dev-scripts inside the Avalonia sample, which compiles a whole release using the local code.

As for creating a "production-like" release, you do need to build velopack separately on windows, linux and mac first, before then putting them all together with /p:PackRustAssets=true. The current production build is very complex and is not really viable locally or repeatable outside of CI at the moment.