mirror of
https://github.com/open-source-parsers/jsoncpp.git
synced 2024-12-27 11:21:02 +08:00
e9ccbe0145
* update example directory
* modify some compile error.
* update with clang-format
* update
* update
* add_definitions("../include/json")
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# Date: Wed Jul 10 21:26:16 2019 +0800
#
# On branch code_example
# Your branch is up-to-date with 'origin/code_example'.
#
# Changes to be committed:
# modified: example/CMakeLists.txt
#
* change CMakeLists.txt
* update streamWrite.cpp
* update
* Update readFromStream.cpp
* fix typo
14 lines
1.1 KiB
Markdown
14 lines
1.1 KiB
Markdown
***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.
|