Re: [Wxlua-users] wxLua Compiles and works in Linux

[Francesco M. <f18...@ya...>]

Hi,

Sorry but I'm missing the point of this discussion; maybe because it's late here ;)
I don't understand if the problem is:

1) be able to build wxLua against different wxWidgets configurations
    (which can be solved using as output dir lib/$(COMPILER)_[dll|lib])

2) be able to build wxLua with different luasetup.h files
    (which I would solve, on win32, using the same approach taken by wxWidgets, see below).

3) both

I guess the problem is mainly #2... in this case:


>> The biggest problem, I think, is how to use two luasetup.h files
>> without having to copy the new one into place between builds.
>>  
> Right, i see. Maybe the wxWidgets way of copying the setup.h to some the 
> lib dir first before starting to compile. That is: it only copies it if 
> not already there.
as Klaas said, wxWidgets keeps a different setup.h for each different combinations of
SHARED/BUILD/UNICODE options. If the corrispondent setup.h (located in 
$(WXWIN)/lib/$(COMPILER)_[lib|dll]/msw[ud]/wx/setup.h IIRC) does not exist, then a default 
one is copied there.

So for the user it's "easy" to customize his wx builds: he creates its setup.h (probably 
modifying the default one) in the right folder and then gives the makefile command.
This system works even for IDEs...


> This in combination with a build/lib directory to be set by the user, 
> will do the job, not? 
well, the user-customizable BUILD folder is not required - but having implemented that for 
wxArt2d, I think I could add it to wxLua, too ;)

>If the 
> $WXLUA_BUILD/lib/vc_lib/mswXXX/wxLua/luasetup.h is found first, at least 
> one can have more then one.
right

> The problem is the to have the makefile use setable output directories 
> for libraries and object files, so one can have several builds.
> I wonder how wxWidgets developers  test  different  setup.h  combination.
I don't know this... but I'd like to ;)

Francesco