Hi,
Francesco Montorsi ha scritto:
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 :)
now wxbind sources, makefiles and default wxluasetup.h are installed on
Unix systems in default paths:
[EMAIL PROTECTED]:~/work/wxLua/gtksud/bin$ l /usr/local/include/wxbind/
totale 1,0K
drwxr-xr-x 3 root root 256 2006-02-03 17:46 build/
drwxr-xr-x 2 root root 136 2006-02-03 17:38 include/
drwxr-xr-x 2 root root 80 2006-02-03 17:35 setup/
drwxr-xr-x 2 root root 1,1K 2006-02-03 16:41 src/
and if the user tries to go in
/usr/local/include/wxbind/build
and types
make -f makefile.gnu WXLUASETUP_DIR=/mydir WXLUABINDLIB_DIR=/home
the wxbindcustom library is correctly built against the wxluasetup.h
found there and goes in /home :))
However I still need to test the wxbindcustom makefiles on win32.
Francesco
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
