From: Francesco M. <f18...@ya...> - 2006-01-28 14:05:41
|
Hi, klaas.holwerda ha scritto: > 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. you are referring to my proposal of making wxStyledTextCtrl as optional, right ? well, I think it would be a nice thing but I do agree that's not strictly required once we document in install.html that one needs to: -> on win32, open contrib/build/stc/stc.dsw and build it (or do the same with makefiles) -> on linux, go to contrib/src/stc and use make install Still, it would be nice to have a fallback. And surely we need to check for it in configure script, at least on Unix. > 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. that could be a choice. John, what do you propose ? > There is also wxstedit which is needed. I didn't know that. It's from wxCode. I'm trying to build it; I'll let you know. Anyway on Unix it would be easy to check for its presence using the AM_WXCODE_CHECKFOR_COMPONENT I created in wxcode.m4 macro file. > Just stop configure if certain things are not available/installed, and > tell what is needed. I prefer those configure which instead of stopping warn you that the feature X is not available and provide a fallback for it :) Francesco |