Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've made following changes :
There is 3 new preprocessor "DEFINE" symbols :
=> if defined, this mean SQLiteCpp is being build/used as a dynamic library
=> if defined, this mean SQLiteCpp is being BUILD as a dynamic library, and it will EXPORT its symbols
=> if not defined, this mean SQLiteCpp is being USED as a dynamic library, and it will IMPORT its symbols
=> if defined, this mean Visual Studio should ignore the DLL export warnings about STL classes. You can ignore that when you build all your solution with the same runtime library. (if you don't do that, you will have very bad time anyway)
I'm not an expert in CMake files, and there is still something to fix in the actual file : the "SQLITECPP_EXPORT" is defined when a dynamic library build is asked, but even to build the example.
The example should not define this symbol because it need to IMPORT the code, not export it.
My guess is a subdirectory with a specific configuration is needed for every target : SQLite3, SQLiteCpp and Example