Hi,
We started with only one incldue path to "$(WXLUA_BASEDIR)/modules"
And use in our files this:
#include "wxlua/include/internal.h"
But now wxluasetup.h creaped in, and requires to add
$(WXLUA_BASEDIR)/modules/wxbind/setup
I wonder if this is wise?
Is they idea to have several wxluasetup.h files, reality?
I am not sure i understand why it had to be in the wxbind module in the
end, but if it is meant for that module, why not put it its include dir?
And include where needed as:
#include "wxbind/include/wxluasetup.h"
or next would be oke too i think.
#include "wxbind/setup/wxluasetup.h"
Like it is now, external librarues/apps need to set two include dirs
again. And if there will be more wxluasetup.h files, the is the begining
of more include paths.
So i suggest to remove the next as include path
$(WXLUA_BASEDIR)/modules/wxbind/setup
and use internal and external to wxLua:
#include "wxbind/setup/wxluasetup.h"
Of is it is in the end not so wxbind specific, make a setup dir within
the modules directory and include wxluasetup.h from there.
#include "setup/wxluasetup.h"
regards,
Klaas
--
Unclassified
-------------------------------------------------------
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
