2008/8/5 Marco Maggi <[EMAIL PROTECTED]> > Ciao, > > I am experimenting with the FFI of Neko on a Linux+GNU system. > I am a little disappointed by the packaging for Linux. > > 1) I have no interest in Apache and mod_neko, so I have no > Apache installed and mod_neko compiling fails; it seems to > me that the only way to turn off mod_neko compiling is to > modify the build system; is this correct?
It seems so, try to rename module name from "mod_neko" to e.g. "__mod_neko" in src/tools/install.neko script (see line 42) > > > 2) The executables under "bin": "neko", "nekoc", "nekoml", > "nekotools" have no documentation for command line > invocation; > am I correct that everything can be done with "neko"? If I > strip the symbols it looks like all these executables are > equal, > is this correct? > What did you mean under "documentation"? Neko is supplied with www/ directory where local nekovm documentation is stored. For compiling neko-scripts (aka foo.neko) you have to use nekoc, for executing compiled scripts - use neko command. > 3) I did a custom installation (to build a Slackware local > package) > and the result is this layout: > > lib/ > lib/libneko.so > lib/neko/ > lib/neko/nekoc.n > lib/neko/nekoml.n > lib/neko/std.ndll > lib/neko/nekoml.std > bin/ > bin/neko > include/ > include/neko.h > include/neko_vm.h > include/neko_mod.h > > by some very basic tests it seems to work; did I left out > something? > hmm... web-based documentation? mod_neko2.ndll also would be useful for some people with Slackware :-) > > 4) Due to personal problems I would really like to have > documentation > in Texinfo format; I am willing to try a conversion from the > available format; is the documentation only available in HTML > from the Neko webpages? > Is seems to be so: only HTML documentation, but some useful comments can be found is source files (take a look at /libs/std/file.c for example). > > 5) A first look at the "Makefile" tells me that the build > system has > important steps written in Neko itself; despite this it > should be > possible to write an Autoconf configuration (no Automake, > no Libtool) > to be used on Linux only; are there known problems or > gotchas one has > to know before attempting? > I afraid the right answer is "No". Neko uses nekoml for building itself. Better ask Nicolas about this point. > 5) The "neko" executable has no command line switching like > "--version", > "--help", "--load" (for modules), "--directory" > (alternative to > "NEKOPATH"), "--compile"; is "main.c" stable enough to > try to add a > command line interface or the fact that some options have > to be handed > to the low level Neko code makes this a problem? (Do not > worry about > the getopts function, I have code of my own) Good question. Ask Nicolas about this ;-) > > Thanks. > -- > Marco Maggi > > "Now feel the funk blast!" > Rage Against the Machine - "Calm like a bomb" > > > > -- > Neko : One VM to run them all > (http://nekovm.org) > -- BR, Vitali Falileev http://insideable.com ICQ: 75008864
-- Neko : One VM to run them all (http://nekovm.org)
