But still when wxbindstc also depends on
wxluasetup.h
better use one wxluasetup.h in:
modules/setup
which both bindings modules do use.
This is actually what i saw today in apps.bkl ??
<!-- always use wxLua's official wxluasetup.h -->
<include>$(WXLUA_BASEDIR)/modules/setup</include>
Klaas
John Labenski wrote:
so I thought that it was a 'cleaner' idea to put wxluasetup.h in
modules/wxbind/setup
instead of modules/setup. After all, wxluasetup.h is a setup for
wxbind, right ?
But that is putting it in a module. While there are already two binding
modules.
I am not sure it they use the same wxluasetup.h, but if yes i would say
it has to be in:
modules/setup
Currently i see a wxluasetup.h in wxbindstc/src too.
or in a new include dir in:
modules/bindings/include
I can imagine that this file can be used module broad for more then
setting bindings on/off.
That's where it gets a little tricky. The wxSTC binding also depends
on the wxLUA_USE stuff, for example wxPoint, wxColour, wxWindow, etc,
but I really don't want to have to go nuts and cross link all the
dependencies since it'll make things very complicated.
I suppose the best solution is to use the wxSTC bindings without any
wxluasetup.h file and in a doc file just state the things that have to
be turned on to make it work. It should be pretty obvious to people
that if they want a complicated widget like wxSTC they have to bind to
a large portion of wxWidgets.
--
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
