Closed AmeliaMesdag closed 3 years ago
Hi,
as far as I'm aware, the dynamic ImGui vcpkg packages are broken as they don't export any symbols ... To work around that, you have these options:
x86-windows-static
, that circumvents the issue as static libs don't need to export anythingadd_subdirectory()
magnum-integration manually with a bundled ImGui (that way it ensures the symbols are exported for a dynamic build), it's the second snippet hereSorry about this, it used to work but we have no control over the other packages in vcpkg, they broke it in one sweeping change (https://github.com/microsoft/vcpkg/pull/5937) and we didn't figure out a solution yet. This issue is also tracked in https://github.com/mosra/magnum-integration/issues/67.
Understood. I'll remove vcpkg and do subtree builds of everything for now.
Vcpkg itself is still useful for the heavier dependencies (although sometimes it's acting up and sometimes just plain cursed) -- one common workflow for users is to have the heavier 3rd party dependencies pulled from vcpkg or other platform-specific package managers and keep just Magnum repos (well, and ImGui) as CMake subprojects.
Good idea. I settled on using the packaged versions of SDL and OpenAL; and compiling Magnum, Bullet and ImGui. Hopefully vcpkg dynamic libraries get sorted out, they're convenient for testing things out.
FYI as of https://github.com/mosra/magnum/commit/62628beac97726468351a1485b01caa5662a0d02 (and mosra/magnum#496) it's possible to bundle SDL2 as well (although doing so increases the CMake configure time quite significantly).
I'm closing this in favor of mosra/magnum-integration#67 to have the ImGui/vcpkg issue tracked in a single place, hope that's okay.
I'm having issues trying to build some of the magnum-examples using Bullet and ImGui, the project was opened in VS 2019 as a CMake project with vcpkg integration. Here's the build output and I've included my configuration.
CMakeSettings.txt
Visual Studio 2019 Config vsconfig.txt
vcpkg listing