From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wxPython/wxWidgets release number mismatch
Date: Wed, 19 Sep 2018 12:33:27 +0300 [thread overview]
Message-ID: <1537349607.5675.4.camel@gentoo.org> (raw)
In-Reply-To: <20180919065827.s6niaglvodksqaan@grusum.endjinn.de>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
Ühel kenal päeval, K, 19.09.2018 kell 08:58, kirjutas David Haller:
> Hello,
>
> On Wed, 19 Sep 2018, Andrew Udvare wrote:
> > Curiosity: what is the reason for wxGTK:3.0 and wxGTK:3.0-gtk3 ?
>
> wxGTK:3.0 uses gtk+-2 and wxGTK:3.0-gtk3 uses gtk+-3.
That, and we couldn't do it with just flipping it to gtk3 in 3.0 SLOT,
because some wxWidgets apps could be doing conditional direct GTK+ code
as well, to go above the lowest common denominator toolkit support that
wxWidgets provides. Or some might just be wrongly linking directly to
gtk2 explicitly. Or had too much trouble with gtk3 in the less used
parts of wxGTK while wxGTK gtk3 support hadn't quite matured yet.
You can't have a program load in (link to) both gtk2 and gtk3 - it will
abort to not go completely runtime crazy and crash due to same function
names. Kind of like wxWidgets itself aborts if the library and app are
using different C++ ABI (however that's less of a problem with todays
relevant C++ ABI updates, unlike the gcc4 to 5 days).
Therefore it was just a separate parallel installable SLOT with which
we could move things over gradually and have the more maintained apps
benefit before everything is working with it.
Mart
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2018-09-19 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 19:48 [gentoo-user] wxPython/wxWidgets release number mismatch Grant Edwards
2018-09-17 20:26 ` [gentoo-user] " Grant Edwards
2018-09-17 20:28 ` [gentoo-user] " Andrew Udvare
2018-09-17 21:02 ` [gentoo-user] " Grant Edwards
2018-09-17 22:45 ` Mick
2018-09-17 23:48 ` Grant Edwards
2018-09-17 23:02 ` Andrew Udvare
2018-09-17 23:51 ` Grant Edwards
2018-09-18 2:01 ` [gentoo-user] " Andrew Udvare
2018-09-18 22:50 ` [gentoo-user] " Mart Raudsepp
2018-09-19 4:13 ` [gentoo-user] " Andrew Udvare
2018-09-19 6:58 ` David Haller
2018-09-19 9:33 ` Mart Raudsepp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1537349607.5675.4.camel@gentoo.org \
--to=leio@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox