-
Notifications
You must be signed in to change notification settings - Fork 47
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 ImGui integration as subdirectory #75
Comments
I've just tested a fresh build and I get this error even when building using shared libraries. |
Welp, I realized after some head scratching that I was including |
Hi! Glad you at least partially solved this already -- I wouldn't be able to discover that without seeing the source. Can you elaborate on how the events are incorrect? Are they not handled at all? Or are they happening at wrong positions? etc. Including relevant parts of the source code would help also, thanks! :) |
😆 was just about to give an update. I verified that the event callbacks and imgui context methods were all correctly getting called. I realized there must be another issue. Onwards! |
Haha 😆 Good to see issues solving themselves if I take ages to reply. |
I just updated the docs to highlight those two common pitfalls a bit better: 1eae551 Not in the online docs yet, will do so in the next upload batch. |
Howdy!
I can compile but not link the ImGui example currently (Windows, VS2019). I get linker errors regarding the event handlers in Context:
My relevant CMake script that sets up Magnum:
And because I set this all up from a subdirectory under the repo root I provide a global interface library to avoid having to repeat myself for anything that uses Magnum:
My application adds
kpns_graphics
to it's PRIVATE target_link_libraries.So, everything compiles fine, CLion resolves all symbols etc. But when linking it fails and I'm not sure why. I'd appreciate any helpful advice.
Thanks!
The text was updated successfully, but these errors were encountered: