You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -140,10 +140,11 @@ The benchmark program reads `data/data.txt` which contains file names of JSON to
140
140
3. Copy premake5 executable to `build/` path (or system path).
141
141
4. Run `premake.bat` or `premake.sh` in `build/`
142
142
5. On Windows, build the solution at `build/vs2015/`.
143
-
6. On other platforms, run GNU `make -f benchmark.make config=release_x32 && make -f nativejson.make config=release_x32` (or `release_x64`) at `build/gmake/`
143
+
6. On other platforms, run GNU `make -f benchmark.make config=release_x64 && make -f nativejson.make config=release_x64` (or `release_x64`) at `build/gmake/`
144
+
-`make -f jsonstat.make config=release_x64`
144
145
7. Optional: run `build/machine.sh` for UNIX or CYGWIN to use CPU info to generate prefix of result filename.
145
146
8. Run the `nativejson_release_...` executable is generated at `bin/`
146
-
9. The results in CSV format will be written to `result/`.
147
+
9.The results in CSV format will be written to `result/`.
147
148
10. Run GNU `make` in `result/` to generate results in HTML.
148
149
149
150
For simplicity, on Linux/OSX users can simply run `make` (or `make CONFIG=release_x32`) at project root to run 4-10 above.
0 commit comments