Coming from the c/c++ cross compiling world I found that NIM might be quite helpful. I am currently re-porting the NIST fingerprint library from C# to C (another approach by another group was not 100% convincing).
What might be helpful for other projects is the configure/autoconf/libtool environment I use. I ported it from my other x-compiling stuff so I can use it for other projects later. It can pull the full NIM/NIMBLE environment from GitHub or just using a local environment (I found that NIM on Debian/Sarge was incomplete). You find my current approach on [http://github.com/mjfh/libAFIS](http://forum.nim-lang.org///github.com/mjfh/libAFIS). Forget about my NIM application code there (I am still learning) but look at the README or .travis.yaml to see how to use it. My goals for the toolchain are: * developer bootstap needs autotools but the distribution needs only a Bourne shell/make/C/C++ etc * target system can be x-compiled (stubs are in but no useful target at the moment) * pre-processing/code generator needs no extra 'configure' pass (eg. CC_FOR_BUILD) as NIM can do that job as well * library generator (using libtool) is provided as a test example Thanks for providing NIM.
