Differences between version #8187 and #8188

39c39
< The C++ runtime used built-in garbage collection that requires cooperation from all haxe threads to synchronize when a garbage collection is performed.  In a single threaded application, it is not really necessary to worry about this, however it is best to do the right thing in case someone wants to use you library in their application.
---
> The C++ runtime uses built-in garbage collection that requires cooperation from all haxe threads to synchronize when a garbage collection is performed.  In a single threaded application, it is not really necessary to worry about this, however it is best to do the right thing in case someone wants to use you library in their application.
41a42,48
> 
> You do not need to do this for neko, but is does not hurt to leave to code in there.
> 
> ===== Building Using the HXCPP Build-tool =====
> 
> There are a several advantages of using the hxcpp built-tool to build your ndll.  The most obvious ones are that it is cross-platform and low-dependency.  Since it uses neko and haxelib to do the work, you do not have to worry about installers etc, and you can be reasonably sure that anyone who is interested in building a haxe ndll is going to have the required files right there on their machine.  This even applies if you are primarily interested in neko - all you have to do is "haxelib install hxcpp" to get the build too, and avoids the need to get "make" for windows, or "Visuall Studio" for Linux.  The cross-platform library stuff is used for the C++ backend, so you will benefit from any improvements performed for that project.
>