Re: luasetup.h and wxLua build system (was Re: [Wxlua-users] wxLua Compiles and works in Linux)

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

Hi,

klaas.holwerda wrote:
> Francesco Montorsi wrote:
>> So, reformulating the problem: wxLua doesn't care about build 
>> settings. The user must be able to build wxLua(bind) using exactly the 
>> same build settings (SHARED,BUILD,UNICODE, I mean) but with different 
>> luasetup.h files.
>> So, copying luasetup.h as wxWidgets does, won't absolutely work, right ?
> 
> 
> In principle the copy is already made, to your own project. It has 
> nothing to do with SHARED, UNICODE etc.
> Still for one luasetup.h all those type of builds ( synchromized with 
> the wxWidgets in WXWIN) should be generated. They do not variate with 
> lausetup.h, but only because of build type.
ok, that is: we want separate build folders for different build settings and not only 
(through the WXLUASETUP_DIR and WXBIND_TARGET_LIBDIR options) for different luasetup.h.
Anyway this is already in place; i.e. object files are sent to the 
build\msw\[compiler][u][d] folder and library files into lib\[compiler]_[dll|lib]).
So, no problem ;)


>>> 4) In the makefile for wxluabind we have
>>> WXBIND_TARGET_LIBDIR = $(WXPREFIX)/lib (or whereever)
>>> so that again, in your own project files you can do
>>> WXBIND_TARGET_LIBDIR = /some/path/to/somewhere/else
>>>
>>> Now you can have two different libs for two different luasetup.h at
>>> the same time.
>>
>>
>>
>>    nmake -fmakefile.vc WXLUASETUP_DIR=c:\myproject\include 
>> WXBIND_TARGET_LIBDIR=c:\myproject\lib
as you said, we also need to send object files there, not only the generated library 
otherwise the object files for the user-luasetup.h could conflict with other builds of wxLua.



>>> HOWEVER! This cannot be made to work for MSVS dsp files, can it?
>>
>>
>> right; unfortunately IDEs do not allow you to specify options which 
>> are in "string" form. That is, you can make multiple configurations in 
>> a DSP file for an option which has a finite set of possible values 
>> (like BUILD=debug/release) but you can't do that for a "path" option.
> 
> 
> Hmmm, i really see /I$(WXWIN)\lib\.
> Is that not enough to do the trick ?
I forgot about environment variables.
But you're right; they could solve the problem: we ask the user to set a WXLUASETUP_DIR 
and WXBIND_TARGET_LIBDIR env variables and then use these in the DSP.
However this means that just downloading wxLua and open the DSW file won't work: the user 
will also need to set the env variables first as this way do not allow to specify a 
"default-value-in-case-the-env-var-is-missing"...

So I don't know if it's better to limit project files to the default luasetup.h or to 
force them to look for the WXLUASETUP_DIR and WXBIND_TARGET_LIBDIR env vars...

Francesco