Hi list,
I made a change in the Neko CVS. There is now a way to "link" dependent
bytecode files together by using the neko compiler. The compilers are
then now provided as a single fat .n bytecode file (in the /boot directory).
One change is that the command to run the Neko and Nekoml compilers is
no longer "nekovm neko/Main ...." or "nekovm nekoml/Main ..." but
simply "nekovm neko ...." and of course "nekovm nekoml ....".
You can run the linker by running :
nekovm neko -link out.n file1.n file2.n ...
It will also automaticaly try to find the static dependencies in each
bytecode and link them together. A "static" dependency is represented by
the bytecode of the expression :
$loader.loadmodule("constant string",$loader)
since all modules are dynlinked in Neko.
The next step is to be able to create a "boot.bin" file to which we can
append the bytecode in order to create standalone binary (you'll still
need libneko.so and .ndll libraries you're using). Of course if you have
precompiled boot.bin libneko.so and std.ndll available for
Linux/Windows/OSX then you can use Neko on Linux to make Windows
binaries which is quite nice.
Nicolas
---
Neko : One VM to run them all
