Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
J
json
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
json
Commits
3eb1b2a7
Commit
3eb1b2a7
authored
Apr 15, 2015
by
Niels
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #59 from dkopecek/master
Fix compilation of json_unit with GCC 5
parents
4c55ada0
ad6ad4ae
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
4 deletions
+5
-4
Makefile
Makefile
+1
-1
test/unit.cpp
test/unit.cpp
+4
-3
No files found.
Makefile
View file @
3eb1b2a7
...
...
@@ -13,7 +13,7 @@ clean:
# build unit tests
json_unit
:
test/unit.cpp src/json.hpp test/catch.hpp
$(CXX)
-std
=
c++11
$(CXXFLAGS)
$(FLAGS)
$(CPPFLAGS)
-I
src
-I
test
-Dprivate
=
public
$<
$(LDFLAGS)
-o
$@
$(CXX)
-std
=
c++11
$(CXXFLAGS)
$(FLAGS)
$(CPPFLAGS)
-I
src
-I
test
$<
$(LDFLAGS)
-o
$@
# create scanner with re2c
re2c
:
src/json.hpp.re2c
...
...
test/unit.cpp
View file @
3eb1b2a7
...
...
@@ -10,9 +10,6 @@
#define CATCH_CONFIG_MAIN
#include "catch.hpp"
#include "json.hpp"
using
nlohmann
::
json
;
#include <array>
#include <deque>
#include <forward_list>
...
...
@@ -24,6 +21,10 @@ using nlohmann::json;
#include <unordered_set>
#include <vector>
#define private public
#include "json.hpp"
using
nlohmann
::
json
;
TEST_CASE
(
"constructors"
)
{
SECTION
(
"create an empty value with a given type"
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment