CopperSpice Forum

At first this seemed like a better idea, but digging around trying to separate all these libraries turns into a nightmare on a bigger project. I also notice that not only do Microsoft themselves still use this "d" naming convention, all my other dependencies that build with CMake seem to f...

I use MSVC.

I build and install CopperSpice on Windows like this: > cmake --build . --config Release > cmake --install . --config Release > cmake --build . --config Debug > cmake --install . --config Debug When I then build my own project, cmake should link against the correct library depending on whether my bu...

When I build CopperSpice I specify CMAKE_INSTALL_PATH=d:\code\third_party\usr\local. This means that when I build software that depends on CopperSpice I provide CMAKE_PREFIX_PATH=d:\code\third_party\usr\local. CMake seems to search for .cmake "Config" files in CMAKE_PREFIX_PATH\lib. So all...

HI Barbara, thanks for getting back to me! I just created a pull request on github for this issue and another small issue where the latest MSVC 19 flags a compiler error in qsslcertificate.h for a redundant declaration. For the record, I am also building boost, nlohmann_json, openssl and Wt (emweb) ...

On Arch Linux, all of my <package>Config.cmake files, including CopperSpice, are installed into /usr/local/lib/cmake/ and everything works fine. On Windows all of my <package>Config.cmake files, *except CopperSpice*, are installed into CMAKE_INSTALL_PREFIX/lib/cmake. CopperSpiceConfig.cmake is incor...