CMakeLists.txt: use transitive compile definitions via cmake#228
Conversation
|
Thank you, this looks promising, but have you seen that all builds are failing? |
|
Oh, thanks, I did not realize! I'll take a look... |
5a6747e to
36181de
Compare
|
Dear @SRombauts, can you help me shed some light on this? I am under the impression that the |
|
Ah I see the issue now. |
…ompile_definitions()
…l over build instructions in CI
8b83c6a to
24564cf
Compare
|
I've copied the define also to the supplied Actually, due to the transitiveness of the new cmake flags, it would be sufficient to only have this option in |
|
Now I see more green lights :-) I hope the PR is fine like this? |
|
Yes, thanks a lot for this! |
|
Thanks to you! |
This PR adds transitive compile definitions via cmake. When this PR is used, a slightly more "modern" syntax is employed for the compile defines
SQLITE_ENABLE_COLUMN_METADATA,SQLITECPP_ENABLE_ASSERT_HANDLER, andSQLITE_USE_LEGACY_STRUCT. With this more modern syntax, its possible to specify for every flag aPUBLICorPRIVATEvisibility. WithPUBLICvisibility (currently the default in this PR), downstream projects also have access to the flags.This can be specifically helpful for
SQLITE_ENABLE_COLUMN_METADATA, which downstream projects can use to tweak their code at compile time.Please feel free to change the visibility of the individual flags. The previous default (before this PR) was
PRIVATEvisibility for all three flags.