Go to file
2024-05-04 01:57:06 +02:00
_constraints Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
_multibuild Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
.gitattributes Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
autoconf-2_72.diff Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
README.SUSE Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
soversion.diff Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxpython-mkdiff.sh Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxWidgets-3_2-Fix-test-suite-on-Linux-s390x-architectures.patch Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxWidgets-3_2-rpmlintrc Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxWidgets-3_2.changes Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxWidgets-3_2.spec Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02:00
wxWidgets-3.2.4.tar.bz2 Sync from SUSE:SLFO:Main wxWidgets-3_2 revision 54e261383edc70a1aa66b736424db07a 2024-05-04 01:57:06 +02: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.