-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add a compilation of the project as a static library #549
Comments
Hi @yannlabou would you like to have a look at this? It should be interesting to implement. I can help with deployment part as I know how to do it. |
Sounds interesting. Will look deeper at it tonight. |
👍 |
@yannlabou you could have a look into this project which I maintain for check how deployment is done. |
Which part of https://github.com/ihhub/fheroes2 should I particularly check? Further it will be better to create to separate issues for the creation of a static and a dynamic library. |
@yannlabou I referred this project as an example for deployment part. In .travis.yml I've added:
to do not run job on specific tags.
|
For appveyor.yml:
to do not build on new tags. Prepare files for deployment (zip archive):
Do deployment:
|
Moreover, I'll create a deployment account for this project soon which will be responsible for all this stuff. |
Okay, I've created a deployment account for this project. |
We would like to integration continuous deployment for the project and one of the goal as of the project is to create it as a static library for end developer who doesn't have specific libraries/technologies on his/her PC. We use Travis-CI as virtual machine server to continuous integration for MacOS and Linux while AppVeyor is for Windows. We use makefile to project compilation for these platforms.
We need to add an ability to compile static library of the project which would go as a part of deployment for releases.
The text was updated successfully, but these errors were encountered: