https://bugzilla.novell.com/show_bug.cgi?id=660438
https://bugzilla.novell.com/show_bug.cgi?id=660438#c9
Stanislav Brabec changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEEDINFO
InfoProvider| |anixx@opensuse.org
--- Comment #9 from Stanislav Brabec 2012-01-09 19:11:46 CET ---
I seen some problems with --enable-compat26 in past. Now we have many variants
of the ABI, so I guess that we can selectively enable on variants where it
works. (Guessing that ANSI and wx container.)
Could you provide links to your binaries for my testing?
Yes the behavior of wxWidgets is counter-intuitive and makes building
cross-distribution binaries that use WxGTK as complicated as possible. But it
is an upstream problem, not downstream.
The upstream did a bad thing: Configure options change ABI, but not always the
library name. So binaries compiled against wxWidgets compiled with different
configure options cannot live together on one system.
That is why openSUSE now uses dedicated directories and compat packages.
See README.SUSE in wxWidgets package?
https://build.opensuse.org/package/view_file?file=README.SUSE&package=wxWidgets&project=X11%3AwxWidgets
Which ABI variant you are using in your third party package?
openSUSE now offers 3 incompatible ABI variants in openSUSE:
- version 2.8.x, ANSI
- version 2.8.x, Unicode, wx container
- version 2.8.x, Unicode, STL
and another 9 variants in the openSUSE Build Service.
- version 2.9.x, ANSI
- version 2.9.x, Unicode, wx container
- version 2.9.x, Unicode, STL
- version 2.8.x, ANSI, with debugging support
- version 2.8.x, Unicode, wx container
- version 2.8.x, Unicode, STL, with debugging support
- version 2.9.x, ANSI, with debugging support
- version 2.9.x, Unicode, wx container, with debugging support
- version 2.9.x, Unicode, STL, with debugging support
If you want to use third party binaries compiled against wxWidgets, the
solution provided forces following limitation:
- only one ABI can be used on the system by third party binaries
- you have to install one of "compat" packages
- If you must install more third party binaries using different ABIs, you have
to write LD_LIBRARY_PATH wrapper for all of these ABIs except the one that is
represented by the compat package.
Note that if you are using third party RPM, zypper and YaST will automatically
ask you to install one of these libraries. But it does not know, which of
variants above is the correct one for your application. You have to pick
correct one manually.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.