Hi Steve, On Tue, Sep 25, 2007 at 08:11:10AM -0500, Steve M. Robbins wrote: > I'd ask you to reconsider adding a dependency from both -dev packages > to wx-common. > > In a narrow sense, you are right to say that there is no dependency in > that you *could* build wxWidget-using code without either wxwin.m4 or > wx-config.
I think you've mistaken what I've said, and/or what is actually in the wx-common package. I've never suggested building without wx-config, and it is not provided by the wx-common package. I've said that you _should_ not use wxwin.m4 -- and the reason for that is it calls wx-config in the wrong way, at the wrong time. I've even said that 'as the author of wx-config'. > I'd bet that is a rare case. Not using wx-config? sure. I'd go so far as to say pathological. Not using wxwin.m4? hardly rare, and a sign of people who read and understand the tools they use. > Indeed, wxWidgets is > specifically for cross-platform applications, so I'd expect most of > them to require probing for the library location at build time. Both > build-time probe mechanisms are in wx-common only. You are wrong on two fronts here. There is only one mechanism: wx-config. And it is not in wx-common. It is in the -dev packages of each of the variants that such a probe might find. wxwin.m4 is just a wrapper that hardcodes the result of a wx-config query at configure time. If anything it reduces your ability to easily and quickly build for multiple targets. All dependent apps should use wx-config and depend on the relevant -dev packages they require, which provide it along with the rest of the lib and header files needed. Apps that want more complexity for a less functional build system, can use wxwin.m4 and should depend on the package that contains it: wx-common. > At the very least, please consider adding a note to README.Debian > in both -dev packages as to where one may find wx-config and wxwin.m4. > It took me an hour to find it when I first installed the packages. There is already a package relationship here, the -dev packages Suggest you install wx-common. And we have a package content search thing on the web somewhere iirc. And you didn't get wx-config from wx-common, so I'm still not sure what other advice I can offer that would have helped you there ... If we can identify a useful note to add, then sure, but this hasn't exactly been a heavy faq, so I don't really know where heavier signage would be the most help. Are people more likely to actually read a README than they are to take notice of a Suggested extra package? Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
