-
Notifications
You must be signed in to change notification settings - Fork 53
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
Way to programmatically generate a standalone release (or statically linked executable) #53
Comments
This has been on my wishlist for a while, and maybe it's time to implement it. You can currently build static binaries by adding the However, it would be (much) nicer if there were a command line option like |
How does the Also, current documentation for the |
Is there a way I can either 1) take the executable I'm building and instruct bake to build all of its libraries as static libraries then link them into the executable, or 2) programmatically get all the libraries depended on so that I can copy them into a directory to bundle alongside of the executable for a standalone release?
I've looked into the various configuration options and haven't found anything yet in regards to doing either
While it would be possible to manually do it myself because I do generally know where bake keeps the libraries, it would be pretty helpful to not have to do this pretty major step in the release process of, say, a game, manually.
The text was updated successfully, but these errors were encountered: