From: Francesco M. <f18...@ya...> - 2005-06-12 14:02:33
|
Hi, >>1) I see wxLua\src & wxLua\include are not listed in dirs.txt; should >>they be removed ? > Yes, but let's leave them for now since they still have one file in > them that Ray says he doesn't want, but it probably wouldn't hurt to > let it be for a bit. ok, no problem >>2) The targets which need to be built are: >>- modules\lua >>- modules\wxlua >>- modules\wxluadebug >>- modules\wxluasocket > > for modules/lua you need to build two things, lua.exe the lua > executable and lua.lib the library. lua should be built as a static > lib on all platforms, see the Makefiles and dsp files to see how it's > done. > Maybe you can take a look at these bakefiles to see if they'll work for us > http://lua-users.org/wiki/LuaAddons > http://www.geocities.com/f18m_cpp217828/prog/lua_win32.zip yes, they'll work for us since I created them and uploaded the links above in lua wiki & on my website ;-) >>Do they support shared (i.e. DLL) builds ? > Hopefully yes, I've never build wxWidgets as a DLL, but I copied the > code in the wxWidget's contrib and added WXDLLIMPEXP_WXLUA which > should export things properly. I have no idea about lua itself though. ok, I'll try >>All the output should go to wxArt2d\lib, right ? > No? It goes to wxLua/lib for the libraries and lua.exe goes to > wxLua/bin this is a standalone library that anyone can use. oops; I just meant wxLua/lib & wxLua/bin... sorry >>Its output should go to wxArt2d\bin, right ? > > No, it should be built in either wxLua/bin or just > wxLua/apps/wxlua/src/vc_xxx for VC for example, in much the same way > wxWidgets builds it's samples. again I mistyped the path... >>4) in wxLua\bindings\wxwidgets there are some CPP & H files; should they >>be built as a library ? >>If yes, how should that lib be called ? > > No, for now they're included directly into the wrappers which is > probably the simplest solution for now. Thew whole wrapper thing is > going to change somehow... ok > Maybe we could put apps/wxlua/build into just apps/build to simplify things. right, that makes things more simmetric :-) >>to build the project, the user should just go to wxlua\build\msw and type >> >>nmake -fmakefile.vc WX_UNICODE=0/1 WX_SHARED=0/1 .... > > > That would be great, maybe we could also have a dsw file as well, see > apps/wxlua/src/wxLua.dsw that can build all the libraries using "batch > build" just like wx.dsw. sure; exactly like wxWidgets also have DSW/DSP files. >>PS: I see that exists a file called luasetup.h in >>wxlua\bindings\wxwidgets; what is its use ? should it be generated by >>some tool/makefile ? > When you run bindings/wxluawrap.lua it takes either the luasetup.h.in > the bindings dir or in your own program's dir and generates luasetup.h > that may exclude other classes automatically using their dependencies. > It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and > Makefile_import to see how the wrappers are generated. It's build is > also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to > generate wxluawrap.cpp, can bakefile do this sort of thing? yes, it can; I'll set up all this stuff when done with modules bakefile; first I'll create modules\build stuff... I'll let you know, Francesco |