Francesco Montorsi ha scritto:
John Labenski ha scritto:
On 5/17/06, Francesco Montorsi
<[EMAIL PROTECTED]> wrote:
Hi,
I'm experimenting with wx module and I've got a few proposals for
it:
1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an example,
isn't it ? Shouldn't then go in wxLua/samples ?
wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?
Eh... I think these are pretty specialized. But, you're probably
right, once things work they should be moved. I just put them into the
dir where I generated the shared lib since I was having trouble with
the paths for require.
Ok, another thing which now comes to my mind: "luamodule" directory
should probably be moved too, in wxLua/modules. In fact, it does not
build any application at all, just a .so/.dll
BTW: I'd organize the thing as:
-> wx.so/dll is always placed in wxLua/lib (even if, in Unix, you're
building from a different build folder, e.g. wxLua/mybuild)
-> luamodule.wx.lua sample uses
package.cpath = ";;../lib/?.so;..\lib\?.dll"
before the call to require("wx")
-> on Unix, wx.so is installed in $prefix/lib/lua/5.1
Now, developers using wxLua which want to ship an application entirely
written in wxLua, which uses the require("wx") notation, will just need
to ship:
-> all DLLs/.so of wxLua/lib if they built wxLua as a shared library
(SHARED=1)
-> wx.so/.dll if they built wxLua as a static library (SHARED=0).
In fact, wx.so/.dll should be built regardless of the SHARED option
value: when SHARED==1, it will just be a super-small file which tells
the OS to load the other .so/.dll libraries; when SHARED==0, it will be
a bigger lib (on my Unix, it is about 9,4 MB) which is self-contained.
What do you think ?
Trying to get wx.dll working on Win32, too, I've found a lot of problems
in building the DLLs of wxLua.
In particular, it looks like the different modules need somehow stuff
which is in other modules to link so that I ended up to compile first
all files and then link them all together in a single monolithic DLL
library.
This is 99% because all modules use the same WXMAKINGDLL_WXLUA symbol
while for various reasons they should use different ones for the
different modules.
Since, in my personal experience, building as DLL can be a BIG pain (you
have to be very careful about WXDLLIMPEXP symbols, inter-module
dependencies and in general in the entire build system), I propose to
make wxLua buildable as a set of modules when SHARED==0 and as a single
monolithic DLL library when SHARED==1.
What do you think ?
Also, what about moving "luamodule" dir to wxLua\modules ? Can I commit
that change ?
Thanks,
Francesco
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wxlua-users mailing list
Wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
