- 28 Apr, 2015 1 commit
-
-
miloyip authored
Fixes #321
-
- 26 Apr, 2015 2 commits
- 25 Apr, 2015 8 commits
- 24 Apr, 2015 4 commits
- 22 Apr, 2015 3 commits
- 21 Apr, 2015 4 commits
-
-
Milo Yip authored
Introduce option to select default gtest installation
-
Andrii Senkovych authored
This will introduce RAPIDJSON_BUILD_THIRDPARTY_GTEST option. If it is set to TRUE, cmake will look for GTest installation in `thirdparty/gtest` before looking in other places. Current default value (OFF) for RAPIDJSON_BUILD_THIRDPARTY_GTEST represents previous behaviour when system-wide gtest installation is used whenever possible. This commit will as well eliminate problem described in #309 when source directory found is `thirdparty/gtest` while include files are found system-wide. This however won't give the user possibility to select gtest installation to use.
-
miloyip authored
-
miloyip authored
-
- 18 Apr, 2015 2 commits
- 17 Apr, 2015 2 commits
- 16 Apr, 2015 5 commits
-
-
Philipp A. Hartmann authored
According to the C/C++ standards, calling `memcpy(NULL, NULL, 0)` is undefined behaviour. Recent GCC versions may rely on this by optimizing NULL pointer checks more aggressively, see [1]. This patch tries to avoid calling std::memcpy with zero elements. As a side effect, explicitly return NULL when requesting an empty block from MemoryPoolAllocator::Malloc. This may be related to #301. [1] https://gcc.gnu.org/gcc-4.9/porting_to.html
-
miloyip authored
-
miloyip authored
-
miloyip authored
-
miloyip authored
-
- 15 Apr, 2015 9 commits