-
Notifications
You must be signed in to change notification settings - Fork 38
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
Library is built twice #34
Comments
Ah it seems I can overcome it by defining set(BUILD_SHARED_LIBS OFF) on the parent CMakeLists |
Well, I notice that I need BUILD_SHARED_LIBS ON for the parent CMakeLists |
I am having the same issue here. As we are integrating libspatialaudio through git submodule, any usage of global cmake flag (specifically, There seems to be a logical flaw as your team keep both default values to ON here libspatialaudio/CMakeLists.txt Lines 15 to 16 in 6e15883
The ninja compiler of Visual Studio 2019 will error out saying there are multiple build rules for libspatialaudio If setting these Cmake options both ON are your intention, did you consider using a private option like |
When using this library as a dependency called from a higher CMakeLists, when compiling with ninja an error is raised because the library is built both as a shared and a static library:
https://github.com/videolabs/libspatialaudio/blob/master/CMakeLists.txt#L15
Is there a way to avoid this and have it only built as shared for example?
The text was updated successfully, but these errors were encountered: