Noissue - Use meson to build the C++ code

README.md

Index: README.md
===================================================================
--- a/README.md
+++ b/README.md
@@ -13,33 +13,47 @@
 
 In order to improve performance and memory usage, some of the code (located
 inside the `compiled` directory) is written in C++ and compiled to JavaScript
 via Empscripten.
 
 ### Requirements
 
 * [Emscripten 1.37.3](https://github.com/kripken/emscripten)
-* [Python 2.7](https://www.python.org)
+* [Python 2.7 & 3](https://www.python.org)

[Wladimir Palant, 2017/12/14 10:57:01]

Python 3 is a transitive dependency for Meson, we shouldn't be mentioning it
here explicitly. E.g. it isn't unthinkable that some future Meson distribution
for Windows will install its own Python 3 copy - a user who follows our
instructions here will have wasted time installing Python 3.

[hub, 2017/12/15 17:44:55]

Done.

+* [meson 0.43.0](https://www.mesonbuild.com)
+* [ninja](https://www.ninja-build.org)
+
+Make sure that meson and ninja are in your PATH.
 
 ### Running Emscripten
 
-After installing and configuring Emscripten you can run the following command:
+After installing and configuring Emscripten you can setup the build
+with the following commands:
+
+    meson build
 
-    python compile
+By default it will create a debug build. Pass `--buildtype release` to
+create a release build.
+
+Then to build just do:
+
+    ninja -C build
+
+This will regenerate the build files as needed.
 
 This will produce a `lib/compiled.js` exporting the classes defined in C++ code.
 
 ### Technical details
 
 Compilation is currently a two-step process. In the bindings generation step,
 the source files are compiled into `compiled/bindings.cpp.js` with the
 `PRINT_BINDINGS` symbol defined. This application is then executed via Node.js
 and will print JavaScript wrappers for the C++ classes to
-`compiled/bindings.js` according to definitions within the `EMSCRIPTEN_BINDINGS`
+`build/bindings.js` according to definitions within the `EMSCRIPTEN_BINDINGS`
 macro in `compiled/bindings.cpp`.
 
 In the actual compilation step the source files are compiled into
 `lib/compiled.js` without the `PRINT_BINDINGS` symbol, so that the
 `EMSCRIPTEN_BINDINGS` macro ignores its contents and merely emits some generic
 functions necessary for the JavaScript bindings to work. The previously
 generated `compiled/bindings.js` file is added to the end of Emscripten output.