I see I'm not the only one having problems.  In order for other binary modules to work with wxLua, wxLua needs to link against a seperate Lua.DLL, a DLL which the modules also link against.  In the current binary release of wxLua the only way to make it work is to rebuild all of the modules and have them link against wxLua.dll to get the lua symbols.

Please please please add/fix the SHARED options to the build system :)


I have 3D rendering working inside a wxFrame using wxLua and IrrLua. 

http://irrlua.sourceforge.net/14.wxWindow.lua

  Unfortunately it only works with wxLua 2.4 due to the linking issues I've described above, which this SHARED option would solve.

  Linking against the LuaBinaries would be best of all.  If everybody links against the same binaries, all of our modules will play together without the need for a recompile somewhere.  Just download the .DLL/.so and go.

" 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 ? "





Ring'em or ping'em. Make PC-to-phone calls as low as 1ยข/min with Yahoo! Messenger with Voice.

Reply via email to