On Thu, 28 Jun 2018 at 08:18, Jason Heeris <jason.hee...@gmail.com> wrote: > > If those modules are not intended to be used outside of the final shader library, then why not to make them static libraries? > I'll test it on the real thing and see how that goes. The only problem I encountered was that the final shared library complains about having "NO SOURCES given to target: module3_dll". I can add "module3.c" as a source, even though technically the static lib should already contain everything from there. I'm not sure why that's an issue though.
So I went and tried this on the real project, and it seems like compiling the static libs into a DLL doesn't give the same results as using the obj files directly, as per my initial list of commands. Namely, some symbols seem to not be getting exported, and some flags are mismatched between compiler and linker. It *could* be due to certain compiler flags, which I've raised in another thread. But I need to either add some test code to my sample project that loads and uses the DLL to demonstrate what's wrong, or identify what's different in the real project that's causing this. It'd be nice if there were a way to get CMake to traverse the dependency graph and just apply specific build commands to each module, even just to debug exactly where this is going wrong, but I don't think I'm up for that challenge just yet. Cheers, Jason
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
