-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Error when trying to configure a cmake build for static linking #1283
Comments
wheres the rest of the cmake output? i dont see any error? |
@braindigitalis the entire output is all there. The errors are at the bottom:
|
do you have vcpkg installed on your system? DPP is trying to enable building using vcpkg which is not working on 10.0.32 which is why it isnt released there yet. |
@braindigitalis unfortunately the same errors still occur:
I don't think I have vcpkg on here (certainly never used it). |
i think the problem is with static linking in general. I am not sure of the fix right now, but we'll come up with something. Until then are you able to use dynamic linking as a workaround? |
Yes dynamic linking works fine, appreciate you looking into it! |
I think this stackoverflow post may be relevant, but I haven't looked deeply enough at the dpp cmake config to confirm it: https://stackoverflow.com/questions/40183810/why-does-cmake-export-require-static-libraries-used-to-build-a-shared-library |
There is a PR #1290 which should fix this once it makes its way to master. |
Closing as #1290 has been merged. |
Git commit reference
a1a32d2 (v10.0.32)
Describe the bug
I'm attempting to build my bot with dpp statically linked. This is the FetchContent config for dpp that I'm using:
And here's the output of running the configure command for the build:
To Reproduce
Steps to reproduce the behavior:
cmake -B build -D CMAKE_BUILD_TYPE=Debug
with the above cmake config to pull in dpp.Expected behavior
Cmake configures the build without errors.
Screenshots
N/A
System Details:
Additional context
The above config works fine for a shared lib build.
The text was updated successfully, but these errors were encountered: