-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to distribute finished game to one directory with CI? #298
Comments
Sorry, I'm not sure :-(. There's Here's what I used to do in my game when I was using tcod: It's not super pretty, but it worked. This was before any of the CIs (that I knew) had Windows, Linux and Mac support so I had a separate scripts for each platform. Note that at least on Linux (and I'm pretty sure Mac too) just copying the DLL next to the binary does not work. You need to either set the right environment variables (e.g. |
This is very important information, because the task is very popular in home gamedev, but the information is impossible to find. Thank you, you really helped. I will try to finish my CI config. Maybe some of this information should be added to the README/Wiki? |
Yeah absolutely. Would you be open to putting up a pull request at some point? I'd prefer to have it in the readme (or a separate file linked from there if it's too big) -- that way it's always there if you clone the repo. |
Yeah, I'd like to, but not soon. I need to resolve this issue in my playground project first.
OK 👍 |
Is there an easy way to automate copying shared libs to a binary location for all three platforms (win, osx, linux)? For example for Travis? The problem is that when i use
cargo build --release
, it puts shared libs in paths likebuild/tcod-sys-395905244d0762cd/out
, and i don't know what commands i should use to create a release ZIP for all platforms.The text was updated successfully, but these errors were encountered: