Hi group,
I'm interrested by using luvit on my ARM embedded device. But, I'm little bit confused about how to do this...
Actually, I began to use node.js on my embedded device to implement quickly an API REST. I was enjoying it until I saw the memory consumption. 36Mb ! So, after a couple of search on internet, I found luvit and this is why I'm here right now.
So, here some points which annoying me:
* I use buildroot. So, I can do cross-compilation very easily with this tool. As I understand, I need to cross compil the luvi tool. After that, I will be able to generate the luvit and lit binaries from my ARM device. But this workflow doesn't allow me to generate the luvit and lit binaries from my amd64 computer and buildroot. Am I right ? Is there a way to cross-compil the luvit program from my amd64 to my arm5 arch (armv5tejl) ? As I understand, I can use lit from my computer to retrieve and update lua files (this is what I did with npm for node.js) so I don't have the need to cross-compil lit.
* Moreover, I saw in the luvi repository the use of git submodule to retrieve openssl, luv, zlib, ... And, the makefile generates a static binary with all dependencies in it. Not really a good thing for me who use embedded device with few memory available... It would be nice to have a binary with dynamic link to these shared libraries. Why don't you use autotools ? It will be easier to cross-compil and will make me happy :) If you don't familiar with autotools, I can give you some help about this.
Otherwise, can I use directly the lua source code of luvit with the lua interpreter ? Maybe I can make a bootstrap program in C to emulate your luvit binary ?
Anthony.