As in the title, I would like to understand the compelling reason to force a static runtime for the library (https://github.com/SRombauts/SQLiteCpp/blob/master/CMakeLists.txt#L24).
This is an issue for any project that wants to use SQLiteCpp, but also has to link to shared libraries (e.g., LGPL). Additional information in this SO answer: http://stackoverflow.com/a/4307551/2741329
I believe that a possible solution would be to adopt a CMake option similar to what gtest provides (i.e., gtest_force_shared_crt), so that user can decide the kind of runtime.
Incidentally, such an approach might also solve #53 without the need to add the export decorations as proposed in #57.
As in the title, I would like to understand the compelling reason to force a static runtime for the library (https://github.com/SRombauts/SQLiteCpp/blob/master/CMakeLists.txt#L24).
This is an issue for any project that wants to use
SQLiteCpp, but also has to link to shared libraries (e.g., LGPL). Additional information in this SO answer: http://stackoverflow.com/a/4307551/2741329I believe that a possible solution would be to adopt a CMake option similar to what
gtestprovides (i.e.,gtest_force_shared_crt), so that user can decide the kind of runtime.Incidentally, such an approach might also solve #53 without the need to add the export decorations as proposed in #57.