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 use? #4
Comments
If something is wrong/missing/unclear, please reply. Create an experimental buildThis will create a build (including vs2017 solution) in the
Submit your experimental test results to cdashRun this command as well before running the
The experimental script does currently only support static 3rdparty libs.
Do you think the windows build needs dynamic linking? |
A few remarks:
|
Also, if I want to test a new feature in debug, and then test it in release, I have to do this all over again? |
First of, thanks for the feedback. The reason that one cmake configuration invocation does only allow to build either release or debug is that not all Currently, the experimental script does always build in the experimental subdirectory. |
Still working on the conan port. There still are some linking problems but I foresee it working in the near future. Once conan is working, this cmake multi generator will be useful |
@cornytrace Can you check rwengine/openrw#508? More specifically, the steps
Please tell me if some command is wrong. |
IDE: MSVC2017
How can CMake automatically find the libraries compiled in this repo?
I have tried setting the CMAKE_PREFIX_PATH to it, but then the bullet debug libraries are not detected.
Furthermore, how do I do a static library link vs a dynamic library link?
The text was updated successfully, but these errors were encountered: