On Sun, Jul 29, 2007 at 08:53:47PM -0500, Steve M. Robbins wrote: > On Sat, Jul 28, 2007 at 11:58:09PM +0930, Ron wrote: > > > 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.
No, by "all of them" I really mean ALL of them, including wx2.4 and any of the infinite number of local flavours people may build for themselves and install concurrently, none of which depend on, or are even necessarily compatible with the distro wxbase2.6 package. > 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. ... so this is incongruent with the Big Picture. > Or simply make libwxbase2.6-dev depend on wx-common. but this is closer to correct. Though its not a dependency as such, libwxbase works perfectly well without this package. It's the app you are building that has the dependency on this extra file. > > 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. Ahh, then you ignored the Suggests of the gui package to (not) install this extra component. Sorry, I thought when I wrote the last mail that one was actually a Depends. But it isn't and doesn't have to be. People who don't need this, don't need it, they can use libwx fine without it. That you reported this against wxbase rather than the gui lib threw me into wrong thinking. The wx-config of the gui lib is not provided by wxbase at all, so wxbase sort of has nothing to do with your problem at all, except to note its missing a Suggests, or maybe Recommends that the gui lib has always covered for. This only affects users of wxbase without any gui lib, of which I believe there are almost none. > 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. Well it's your choice how much or little you care to interact with the authors of things you use, I'm not aiming to debate with you about it either, just shedding a little light on a simpler, more reliable, way to do the same thing. If you'd rather add Build-Depends: wx-common for this one, and don't care about the problems of these macros, then that's fine with me too. I was just offering the cleanest answer to the original problem that seemed to be reported. > P.S. Also, for the record, Code::Blocks didn't compile with wxWindows > 2.6 :-( so I'm building wxWindows 2.8.4 locally. Yeah, as you've already noticed 2.8 has a few issues of its own still. There is a apparently another release scheduled sometime soon if anyone finds time to apply patches from upstream bts and do some testing. We'll see how that one looks when it comes out. Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
