Nick Desaulniers (paternity leave)

http://www.muppetlabs.com/~breadbox/bf/

http://www.bf.doleczek.pl/#

http://www.davidsalomon.name/assem.advertis/asl.pdf

Not sure about the js exectubale regarding best practices of having compiler specific build targets. I'll have to do some research, but I think it's doable. @juj probably knows.

so basically, the cmake build script would _have to_ be run twice; once to build the C++ code, and once to build the JS code, possibly removing the cmake cache...

> or set it to build to two different directories So I would have to move the source files into their own directories each with their own CMakeLists.txt?

I was hacking on this a little, I'll upstream some of my patches. The first step was to get everything to build, which I have.

[syscall IDs used](https://github.com/nemasu/asmttpd/blob/master/constants.asm#L72-L92): | name | [Linux](http://blog.rchapman.org/post/36801038863/linux-system-call-table-for-x86-64) | [Apple](http://www.opensource.apple.com/source/xnu/xnu-1456.1.26/bsd/kern/syscalls.master) | same fn signature | | --- | --- | --- | --- | | write | 1 | 4 |...

I think we should use the preprocessor to check for [OS specific symbols](http://nadeausoftware.com/articles/2012/01/c_c_tip_how_use_compiler_predefined_macros_detect_operating_system#OSXiOSandDarwin) and have conditional assembling. [example](https://github.com/girino/jhProtominer-bad/blob/ca99ef58f3235990c457f20133983ec01ed643c1/src/intel/sha256_avx1.asm#L416)

looks like the system call number need to be shifted. I have verified this, will try to find more info as to why: https://filippo.io/making-system-calls-from-assembly-in-mac-os-x/ edit: see also: http://dustin.schultz.io/blog/2010/11/15/mac-os-x-64-bit-assembly-system-calls/