-
-
Notifications
You must be signed in to change notification settings - Fork 67
Rename BUILD_TESTING to QCORO_BUILD_TESTING #233
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
Comments
Hi, Depending on how you are using the library you can turn them off selectively - if you are using ExternalProject, just pass Although I see no harm in adding QCORO_ENABLE_TESTING to disable building QCoro tests, alongside the BUILD_TESTING variable itself. |
This is useful mostly in larger projects where QCoro is included as a submodule and added using add_subdirectory. Setting this variable allows to disable building QCoro tests, while keeping BUILD_TESTING set to ON, so that the main project's test get built and run. Fixed #233
This is useful mostly in larger projects where QCoro is included as a submodule and added using add_subdirectory. Setting this variable allows to disable building QCoro tests, while keeping BUILD_TESTING set to ON, so that the main project's test get built and run. Fixed #233
Examples and testing executables are features that I do not need when consuming the library. Now, I can easily disable them in my
CMakePresets.json
, butBUILD_TESTING
should have theQCORO_
prefix and a dedicated option. Now I have to hope that no other third party library that I use, uses the same flag :)The text was updated successfully, but these errors were encountered: