1
0
Go to file
2023-11-03 10:20:05 +00:00
_constraints wxWidgets development branch that will eventually become 3.2 2014-12-07 00:34:49 +00:00
_multibuild Accepting request 985562 from home:StefanBruens:branches:X11:wxWidgets 2022-06-28 15:43:38 +00:00
.gitattributes wxWidgets development branch that will eventually become 3.2 2014-12-07 00:34:49 +00:00
.gitignore wxWidgets development branch that will eventually become 3.2 2014-12-07 00:34:49 +00:00
README.SUSE wxWidgets development branch that will eventually become 3.2 2014-12-07 00:34:49 +00:00
soversion.diff go to sonumber 9 as there is no symbol versioning that would allow minor number bumps 2023-05-04 07:45:44 +00:00
wxpython-mkdiff.sh wxWidgets development branch that will eventually become 3.2 2014-12-07 00:34:49 +00:00
wxWidgets-3_2-rpmlintrc Accepting request 985562 from home:StefanBruens:branches:X11:wxWidgets 2022-06-28 15:43:38 +00:00
wxWidgets-3_2.changes - Update to release 3.2.3 2023-11-03 10:20:05 +00:00
wxWidgets-3_2.spec - Update to release 3.2.3 2023-11-03 10:20:05 +00:00
wxWidgets-3.2.3.tar.bz2 - Update to release 3.2.3 2023-11-03 10:20:05 +00:00

wxWidgets in SUSE
=================

There are many possible wxWidgets configurations that can be built
from a single source spec file. Depending on what options have been
chosing, the ABI changes in incompatible fashion, yet the library
filenames do not.

To counter running a program with an incompatible variant of
wxWidgets, we chose to make use of the vendor tagging mechanism.
Programs built against the SUSE wxWidgets explicitly require the
library by our name and therefore cannot inadvertently be run with an
incompatible wxWidgets from another distribution.

To run a foreign program, you will need to use the LD_LIBRARY_PATH
mechanism to point it to a directory which contains the matching
third-party wxWidgets variant.