Francesco Montorsi wrote:


More generally this problem (listed as #1 in my "Remaining problems" mail) can be solved only using configure checks at run-time, IMO. This is because while all other features presence can be auto-recognized using wxUSE_* symbols, contrib libs and 3rd party code cannot.
What do you think ?

Why not just put it in install.html. wxWidgets its contrib organization is no good, that is the problem. If one compromizes because others are unable to organize the stuff, that is a bit weird. If this is really such an issue, there is always a thirdparty libs trick, meaning copy it in CVS and use it, if not available somewhere else.
There is also wxstedit which is needed.
Just stop configure if certain things are not available/installed, and tell what is needed.

Klaas



-------------------------------------------------------
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

Reply via email to