[Slackbuilds-users] wxGTK3 (3.0.5) upgrade?
Willy Sudiarto Raharjo
willysr at slackbuilds.org
Wed Aug 10 01:44:17 UTC 2022
> Your wxWidgts buildscript doesn't seem to create the correct wx-config
> links since 3.2 moved the location?
>
> script (pulled from SBo-git wxWidgets-wip branch today):
> # wxWidgets 3.2 provides 2 wx-configs, but we will use GTK by default
> gtk=gtk3-unicode-3.2
> qt=qt-unicode-3.2
>
> if [ "${INTERFACE:-gtk}" = "qt" ]; then
> ln -sf ../lib${LIBDIRSUFFIX}/wx/config/$qt $PKG/usr/bin/wx-config
> else
> ln -sf ../lib${LIBDIRSUFFIX}/wx/config/$gtk $PKG/usr/bin/wx-config
> fi
>
>
> ls -l /usr/bin/wx-*
> lrwxrwxrwx 1 root root 35 Aug 9 10:41 /usr/bin/wx-config ->
> ../lib64/wx/config/gtk3-unicode-3.2
>
> but wxWidgets now uses:
>
> # locate gtk3-unicode
> /usr/lib/wx/config/gtk3-unicode-3.2
> /usr/lib/wx/include/gtk3-unicode-3.2
> /usr/lib/wx/include/gtk3-unicode-3.2/wx
> /usr/lib/wx/include/gtk3-unicode-3.2/wx/setup.h
>
> I thought this might have something to do with building on
> Slackware64-15.0 multilib. However, the same paths above occur when
> building on a pure, clean Slackware64-15.0 (qemu VM).
Hi Ed
yeah i noticed that too (and that's why it's still WIP)
i checked with ARCH Linux and since they don't use lib64 location in
their system, they don't have this issue
my goal is to keep the location separated between x86 and x86_64, but
still haven't got time to fix that path location, hence i haven't
submitted to SBo yet
--
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220810/1859d24e/attachment.asc>
More information about the SlackBuilds-users
mailing list