Red Hat Bugzilla – Bug 189564
wxGTK package not providing virtual wxwin package
Last modified: 2007-11-30 17:11:31 EST
Description of problem:
There's a convention that packages of WxWindows ports should provide a (virtual)
package wxwin, so that packages can depend on the presence of a WxWindows port,
regardless of the toolkit used (e.g., see
http://dag.wieers.com/packages/wxGTK/wxGTK.spec). The FC4 and FC5 Extras
packages don't provide this.
Hmmm. See comment #5 in bug #154618. That's about "wxWindows" rather than
"wxwin", but I think the same logic applies.....
In other words, the packages might connect at the package dependency level, but
they're not going to connect at the link level? If you've built against wxGTK,
it's not going to link against wxqt, because there's a common API at the source
level, but not a common ABI at the link level. Silly me, I figured if the
convention existed, it would actually work.
Teh generated libraries are all things like "libwx_gtk2u_core", and so
presumably "libwx_qt_core" or "libwx_motif_core". So I don't think we even need
to test to see that it won't work.....
I'm going to close this as WONTFIX. Reopen if I'm wrong. :)