[Wxlua-users] Re: Custom wxBind library and wxLua

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

Hi,

klaas.holwerda ha scritto:
>> Anyway, on Unix, it wouldn't be such difficult to provide to the guest 
>> app X the required info to recompile wxLua's wxbind module.
>> It would probably be somewhat more difficult on win32, but probably 
>> still feasible.
> 
> I think setting the variables inside the App its makefiles should/could 
> do the job.
> Why would it be complicated ? If the variabes are set, you the same as 
> with wxbind, but here with different locations.
it is 'complicated' because the app X needs to compile sources located 
in wxLua.

Let's say (on Unix) that the user compiles and installs wxLua and then 
removes the wxLua directory which he used to compile it.
app X is then unable to compile its custom wxbind module since wxbind 
sources do not exist anymore on that system.
This should not be a problem on win32 since if you want to compile app X 
then you probably won't remove the wxbind's sources of wxLua :)

However, let's say that we install wxbind sources somewhere (maybe 
$(prefix)/share/wxlua/wxbind/src and 
$(prefix)/share/wxlua/wxbind/include). Then, on Unix, the app X would 
need to just add to its makefile a call like:

MAKEFILE=`pkg-config wxlua --variable=wxbindcustom-makefile-location`
make -f $MAKEFILE WXLUASETUP_DIR=/myproject/... 
WXLUABINDLIB_DIR=myproject/...   customwxbind

On win32 provided that a WXLUA environment variable exists:

nmake -f %WXLUA%/modules/wxbind/build/msw/makefile.vc 
WXLUASETUP_DIR=/myproject/... WXLUABINDLIB_DIR=myproject/...   customwxbind

Ok, after all it's not that difficult :)


Francesco