forked from pool/wxWidgets-3_2
Jan Engelhardt
249628cd96
wxWidgets is the last consumer of gnome-vfs2 - and I'd really really like to get rid of it osc whatdependson openSUSE:Factory gnome-vfs2 standard x86_64 gnome-vfs2 : wxWidgets-3_0 wxWidgets-3_0-nostl wxWidgets-3_2 - Drop gnome-vfs2-devel BuildRequires, and no longer pass with-gnomevfs to configure, gnome-vfs2 is deprecated many many years ago, and slated for removal from openSUSE Factory. It is currently only used for associating MIME types (in wxWidgets), and we can live without that. OBS-URL: https://build.opensuse.org/request/show/955347 OBS-URL: https://build.opensuse.org/package/show/X11:wxWidgets/wxWidgets-3_2?expand=0&rev=88 |
||
---|---|---|
_constraints | ||
_multibuild | ||
_service | ||
.gitattributes | ||
.gitignore | ||
README.SUSE | ||
soversion.diff | ||
wxpython-mkdiff.sh | ||
wxWidgets-3_2-rpmlintrc | ||
wxWidgets-3_2.changes | ||
wxWidgets-3_2.spec | ||
wxWidgets-3.1.5-fix-wxIcon-wxDVC-columns.patch | ||
wxWidgets-3.1.5.tar.bz2 |
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.