jsoncpp

mirror of https://github.com/open-source-parsers/jsoncpp.git synced 2024-12-26 18:51:04 +08:00

History

* Prevent cmakelint warnings

Use 4 spaces for indent, no tabs

* Use ccache right

fix indents too at CMakeLists.txt

2020-02-13 13:20:46 -08:00

readFromStream

Create an example directory and add some code examples. (#944 )

2019-09-17 13:30:00 -07:00

readFromString

Run Clang-tidy with modernize-use-auto (#1077 )

2019-12-04 09:08:45 +08:00

streamWrite

Create an example directory and add some code examples. (#944 )

2019-09-17 13:30:00 -07:00

stringWrite

Create an example directory and add some code examples. (#944 )

2019-09-17 13:30:00 -07:00

CMakeLists.txt

Use ccache right (#1139 )

2020-02-13 13:20:46 -08:00

README.md

Create an example directory and add some code examples. (#944 )

2019-09-17 13:30:00 -07:00

README.md

NOTE

If you get linker errors about undefined references to symbols that involve types in the std::__cxx11 namespace or the tag [abi:cxx11] then it probably indicates that you are trying to link together object files that were compiled with different values for the _GLIBCXX_USE_CXX11_ABI marco. This commonly happens when linking to a third-party library that was compiled with an older version of GCC. If the third-party library cannot be rebuilt with the new ABI, then you need to recompile your code with the old ABI,just like: g++ stringWrite.cpp -ljsoncpp -std=c++11 -D_GLIBCXX_USE_CXX11_ABI=0 -o stringWrite

Not all of uses of the new ABI will cause changes in symbol names, for example a class with a std::string member variable will have the same mangled name whether compiled with the older or new ABI. In order to detect such problems, the new types and functions are annotated with the abi_tag attribute, allowing the compiler to warn about potential ABI incompatibilities in code using them. Those warnings can be enabled with the -Wabi-tag option.