On Sat, Jul 28, 2007 at 11:58:09PM +0930, Ron wrote: > > Hi, > > On Sat, Jul 28, 2007 at 01:36:21AM -0500, Steve M. Robbins wrote: > > Package: libwxbase2.6-dev > > Version: 2.6.3.2.1.5 > > Severity: normal > > > > I think it is common practice to install all developer tools, such as > > the M4 macros in wxwin.m4 when the -dev package is installed. The > > behaviour of wxwindows surprised me in this regard, since the macro > > file is hidden in wx-common. > > > > Please consider either moving wxwin.m4 or making the -dev package > > depend on it. > > It can't go in the -dev packages, its common to all of them, that's > why wx-common exists. The missing dep for the wx-base package has > gone unnoticed until now though.
By "all of them", I assume you mean the two packages libwxbase2.6-dev and libwxgtk2.6-dev. Since libwxgtk2.6-dev depends on libwxbase2.6-dev, it suffices to fold all of the developer stuff in wx-common into libwxbase2.6-dev. Or simply make libwxbase2.6-dev depend on wx-common. Either change addresses my concern. > I'm not sure what I find more surprising though, that someone is using > wxbase without also needing the gui libs, or that you plan to use > wxwin.m4 to do it ... Just call $(shell wx-config ...) directly from > your own makefiles. It's much simpler, much less prone to doing > surprising things, and doesn't add 12k to your source to do just that. I'm not sure how you managed to jump to those conclusions. For the record, I'm trying to compile Code::Blocks, which is gui-based and thus does use the gtk libs. I'm building it from SVN which means I had to bootstrap the auto-machinery and, in particular, needed the autoconf macros AM_OPTIONS_WXCONFIG and AM_PATH_WXCONFIG. That's why I went looking for wxwin.m4. It's not my code and I'm not going to debate with them how best to find wxWindows. Regards, -Steve P.S. Also, for the record, Code::Blocks didn't compile with wxWindows 2.6 :-( so I'm building wxWindows 2.8.4 locally.
signature.asc
Description: Digital signature
