enginesound icon indicating copy to clipboard operation
enginesound copied to clipboard

More info in building section

Open cryham opened this issue 1 year ago • 3 comments

Hi Great application. I managed to build it, even not knowing this all so it's not difficult, but I would add some more info to readme like: To build this project (written in Rust language) you'll need cargo and I'd add it here too (in deps): sudo apt-get install libasound2-dev libxcb-shape0-dev libxcb-xfixes0-dev cargo Then I'd write some basic info how to build (for others), so:

After installing cargo type (in this folder):
cargo build --release
This can take few minutes, and should say "Finshed" in last line.
Then type:
cargo run
to start the GUI application.
Which is the same as executing binary from /target/debug/enginesound
Building needs about 2GB of space. It can be cleaned, only binary is needed to start.

Lastly I actually got 2GB of stuff now inside /target/debug, is that normal? does it need to be there after build? Tried release and it's that big too. I see that only the binary is needed (can start elsewhere alone), so maybe also adding some info would be good in readme about this 2GB size and cleaning it after when not needed to build. Maybe also add a link for those who don't know Rust: https://doc.rust-lang.org/book/ch01-03-hello-cargo.html

cryham avatar Aug 02 '23 18:08 cryham

What are the packages to build in fedora (dnf), none of the packages can be found. Edit: libasound2-dev is alsa-lib-devel in fedora, I don't about others.

batt0s avatar Sep 28 '23 17:09 batt0s

cargo build --release and then cargo run is not how you are supposed to do things, you're building it twice...

just do cargo run --release.

bend-n avatar Jun 07 '24 13:06 bend-n

Does this engine sound generator work on Windows? If it does, how can I run it?

ZeldaACFan17 avatar Jul 01 '24 16:07 ZeldaACFan17