https://wxwidgets.org/news/2016/02/wxwidgets-3.1.0-released/
wxGTK-3.1.0 is a first development release leading up to stable 3.2 series. I'm not sure we'd want to add it unless we need it for some reason in p.mask or something (maybe as a convenience for devs using wx or something). But up to Ryan I think.
I think we'll only be adding 3.1 if a package explicitly needs it.
*** Bug 591260 has been marked as a duplicate of this bug. ***
(In reply to Ryan Hill from comment #2) > I think we'll only be adding 3.1 if a package explicitly needs it. Apparently games-emulation/dolphin.
wxGTK 3.1.0 includes a fix for bug 592436. At the moment, 3.0 fails to build with GCC 6. See that thread as well, thanks.
(In reply to Ryan Hill from comment #2) > I think we'll only be adding 3.1 if a package explicitly needs it. Any application that allows binding of custom keys for accelerator functions, can use multimedia keys only in 3.1. Eg media-sound/guayadeque
Created attachment 464828 [details] wxGTK-3.1.0.ebuild This is my attempt of an ebuild for wxGTK 3.1.0, based on wxGTK-3.0.2.0-r301.ebuild The differences are : - The source URI is now on GitHub - The archive is wxWidgets-${PV}.tar.bz2 instead of wxPython-src-${PV}.tar.bz2 - I removed the docs archive, as I didn't know how to handle it - I didn't use any patch - I removed some references to 3.0 in the body of functions and put them in the header as variables, like ${WXVERSIONTAG} and ${WXRELEASE_NODOTSLASH} (this one is new) I needed this version for another ebuild that is not in the portage tree, but in Bug 376187
http://wxwidgets.org/news/2018/02/wxwidgets-3.1.1-released/
The ebuild I proposed for 3.1.0 also worked for 3.1.1 on my system, simply by renaming it to the new version number.
there is a small change necessary to proceed wrt the proto packages : the changed part is : X? ( x11-base/xorg-proto[${MULTILIB_USEDEP}] )" I'm currently trying to build this, but this is a bit confusing : The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by wxGTK:3.1-gtk3 (argument) >=x11-libs/wxGTK-3.1.0 -abi_x86_32 Any hints?
x11-libs/wxGTK-3.1.1-r301 and a modified wxwidgets.eclass are available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay
Current cubicsdr requires at least 3.1.1, and the old release in ::gentoo fails to produce any audio output. It is sad the pull request was not applied.
Bump.
3.1.x is still a development release whose ABI will be different compared to another 3.1.x release. Nothing has changed in this regard. If an application requires a development version, then the overall result can't be considered stable and it's arguable it belongs in the main tree.
(In reply to Mart Raudsepp from comment #14) > 3.1.x is still a development release whose ABI will be different compared to > another 3.1.x release. Nothing has changed in this regard. If an application > requires a development version, then the overall result can't be considered > stable and it's arguable it belongs in the main tree. Why not make it a slotted package or stage it in ~*, then?
~arch can be considered stable candidate. wxGTK-3.1.x will never be a stable candidate. There is no manpower right now to maintain this in package.mask for the time being. You are free to take your complaints to upstream for not releasing new feature releases in a sensible release timeline.
https://github.com/perfect7gentleman/pg_overlay/blob/master/x11-libs/wxGTK/wxGTK-3.1.2-r300.ebuild
wxWidgets 3.1.3 Released Posted on October 28, 2019 Please notice that while 3.1.3 is officially a “development” version because it is not fully compatible with the “stable” 3.0.x, the list of backwards incompatible changes is very short, so you shouldn’t have any problems updating to this version from 3.0.x in practice, and you’re encouraged to use this release, including in production.
wxGTK-3.1.3-r300 available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay Tested with cubicsdr-0.2.5_p20191029
Tested (and works) with dev-util/codelite-9999 in my local overlay.
(In reply to Frank Krömmelbein from comment #18) > wxWidgets 3.1.3 Released > Posted on October 28, 2019 > > Please notice that while 3.1.3 is officially a “development” version because > it is not fully compatible with the “stable” 3.0.x, the list of backwards > incompatible changes is very short, so you shouldn’t have any problems > updating to this version from 3.0.x in practice, and you’re encouraged to > use this release, including in production. And there are no guarantees a 3.1.4 will be ABI compatible with this 3.1.3. This is far from production ready in linux distributions. They mainly have in mind using it "in production" when static linking to the wx library in windows and Mac builds, and self-made semi-proprietary linux builds that ship with wx itself.
From the official webpage at https://www.wxwidgets.org/: > wxWidgets 3.1.3 Released > > Posted on October 28, 2019 > > wxWidgets 3.1.3 release is now available on GitHub. [...] > > Please notice that while 3.1.3 is officially a “development” > version because it is not fully compatible with the “stable” > 3.0.x, the list of backwards incompatible changes is very > short, so you shouldn’t have any problems updating to this > version from 3.0.x in practice, and you’re encouraged to > use this release, including in production. A few packages that could be maintained in portage require the 3.1 API, such as freefilesync, for example. This should be available as ~arch at least, as per the upstream statement about it being production-ready. As there have been some portage-specific patches in the 3.0.4 ebuilds, it would be nice if one of the experts on wxGtk on Gentoo would provide at least an ebuild to locally overlay the wxGtk 3.1.3 version in a slot, as an attachment here, if you're still uncomfortable about having it in the official repository. It's unclear which patches out of https://dev.gentoo.org/~leio/distfiles/wxGTK-3.0.4_p20190713.tar.xz are code-related and/or any of them are Gentoo or Portage-specific, so others can pick up from there. I hate to be a nag, but if upstream encourages to use 3.1, then there will be more and more packages actually requiring it. Could there be changes in 3.1.4? Maybe, maybe not. That'll be in upstream's hand, and developers of 3.1-dependent packages will have to deal with it, and recompile, or maintainers of such packages on Gentoo might need a patch here and there. But last time I looked, that's what Gentoo was made for, and why I use and like it. If I wanted outdated binary packages, I'd run Ubunto LTS...
You should direct your nag energy to wxWidgets upstream about releasing a stable feature version then :) If they say it's stable and ABI won't change, then they should release 3.2.0, not wait another year until someone finally decides the remaining new API and features no-one is working on don't need to go into that 3.2 release. We are not Windows, for which they encourage to static link some random development version in there, as ABI stability isn't of concern with static linkage.
Well, it would at least be nice to have an update to wxWidgets 3.0.5, the latest release in the stable 3.0 series. (came out in April this year) However, I'll test whether I can fix #650500 with an update to 3.0.5 or 3.1.4 (will try both), as that bug pesters me for years now.
https://trac.wxwidgets.org/wiki/Roadmap "Development branch and 3.2 New development happens on 3.1 branch. The latest version is 3.1.4, released on July 22, 2020 and we plan to release one last 3.1.5 release in 3.1.x series in the beginning of 2021 with 3.2.0 hopefully following soon after. One of the big planned changes for this 3.2 is better support for high DPI displays, but there are, of course, many, many other fixes and improvements in it as well. 3.2 will also finally drop support for very old legacy systems (such as Win9x platform) and compilers (MSVC6, maybe MSVC7 as well)."
https://trac.wxwidgets.org/wiki/Roadmap "New development happens on 3.1 branch. The latest version is 3.1.5, released on April 14, 2021 and we plan to release one last 3.1.6 release in 3.1.x series in a couple of months with 3.2.0 hopefully following around September 2021."
https://www.wxwidgets.org/develop/roadmap/ "Development branch and 3.2 New development happens on 3.1 branch. The latest version is 3.1.6, released on April 4, 2022. It will be followed by 3.2.0, which will become the new stable branch, soon. The only remaining change that we still plan to implement before 3.2.0 release is the addition of the new API for customizing native file dialogs."
x11-libs/wxGTK-3.1.6-r300 is available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay
wxWidgets 3.2.0 is out: After almost 9 years since the beginning of the last wxWidgets stable release series, the first release in the new stable 3.2 series is finally available on GitHub. You will find there archives with the library sources and documentation as well as binaries for the selected Windows compilers such as Microsoft Visual C++, MinGW-w64 and TDM-GCC. You can also read the updated documentation for this version and, in particular, if you’re new to wxWidgets, you may find the installation guide a good starting point. Changes in this release This release is a culmination of many years of development since the last stable 3.0 release. It contains more than 15,000 commits from more than 400 unique contributors (including more than 200 with multiple contributions) and has too many improvements to list them all here, but here is a maximally condensed summary of the most important ones: Build system improvements: support for new compilers (up to MSVS 2022, g++ 12, clang 14) with an even simpler way of using wxWidgets from MSVS, with wxwidgets.props file, as well as an entirely new CMake build system. Support for native dark mode under macOS 10.14 and later, support for ARM hardware and macOS versions up to 13. High DPI support with the new, but almost perfectly backwards- compatible, API based on wxBitmapBundle, including per-monitor DPI and dynamic DPI changes. New features: HTTPS and HTTP/2 support with wxWebRequest and friends; support for freezing rows/columns in wxGrid; mouse gesture events (GSoC 2017 project); non-integer font sizes and arbitrary font weights in wxFont; fractional pen widths in wxGraphicsContext; arbitrary label windows in wxStaticBox; markup in wxDataViewCtrl items text; support for ZIP 64 files; LZMA compression; much improved accessibility support under MSW; new Edge-based wxWebView implementation; support for using native spell-checking in wxTextCtrl; new PCRE-based wxRegEx. New classes: wxActivityIndicator, wxAddRemoveCtrl, wxAppProgressIndicator, wxBitmapBundle, wxNativeWindow, wxPersistentComboBox, wxPowerResourceBlocker, wxSecretStore, wxTempFFile, wxUILocale and many new features in the existing classes. New XRC handlers for all the new and some of the existing classes. Significant improvements to: wxBusyInfo, wxDataViewCtrl, wxDirDialog, wxGrid, wxNotificationMessage, wxSpinCtrl, wxStaticBox, wxStyledTextCtrl, wxUIActionSimulator. Improvements to compile-time safety with the possibility to disable dangerous implicit conversions between wxString and char* strings. Latest versions of all bundled 3rd party libraries, including all the security fixes and support for WebKit 2 and GStreamer 1.7 under Unix. Better, even if still perfectible, Wayland support in wxGTK. Revamped OpenGL support better suited to modern OpenGL (3.2+). Further C++11 and later support improvements, wxWidgets can be built using C++20 compilers. New experimental wxQt port. Many, many bug fixes. Note that in spite of all these changes, wxWidgets 3.2.0 is almost fully compatible with wxWidgets 3.0 and updating the existing applications to use it shouldn’t require much effort. But please do read the (relatively short) section listing the incompatible changes in the beginning of the change log file if you’re upgrading from a previous wxWidgets version.
A displaycal fork supporting python 3 requires wxWidgets>=4.1.1, so I added this bug as dependency. Looking forward to 4.2 in tree
(In reply to Bernard Cafarelli from comment #30) > A displaycal fork supporting python 3 requires wxWidgets>=4.1.1, so I added > this bug as dependency. Looking forward to 4.2 in tree wxWidgets>=4.1.1, 4.2 really?
Probably needs wxPython at that level, not wxWidgets.
wxGTK-3.2.0-r300 is available in my overlay.
Sorry yes, I got my versions confused (not helped with upstream mixing wxpython and wxGTK when talking about wxwidgets). So for wxGTK it is more 3.2, mostly as requirement for wxpython 4.1.1
*** Bug 873127 has been marked as a duplicate of this bug. ***
Do we need someone creating a PR or does the Gentoo wxWidgets project the bumps soon? Latest Stable Release: 3.2.1 Released: September 9, 2022 API Stable Since: July 7, 2022 I am using https://github.com/stefantalpalaru/gentoo-overlay/blob/master/x11-libs/wxGTK/wxGTK-3.2.1-r300.ebuild The PR in "See also" is dead and closed. Don't forget wxpython and wxwidgets.eclass.
A pull request would be good with the eclass preparations included in it (possible in separate commits, as is logical), followed by active work on it on IRC between me and the PR author with their initiative to keep pushing for it there in discussions with me. That's realistically how we can get that in within a couple weeks timeline. With it left to me without someone doing the active work and poking for reviews and such, I don't see this materializing before December, sadly. I am "leio" on IRC. To reiterate what we should see here in the end: * This is a new SLOT that has to be parallel-installable with the 3.0 slots * We only carry forward gtk3 support, gtk2 support gets dropped in Gentoo with 3.2 * I was going to say that with only a single toolkit option remaining, we can probably name it just "3.2" instead of "3.2-gtk3" and match the ABI version - however, I now see that it is likely the ABI actually IS 3.2-gtk3. See how the libraries are suffixed to decide, e.g. with 3.0-gtk3 we actually have "libwx_gtk3u_adv-3.0-gtk3.so.0" and co. If it remains like that with 3.2, we can have it as SLOT="3.2-gtk3". * wxPython 4.2 bump appreciated as well
Switched to wxGTK-3.2.1. Everything works quite good but wxmaxima. See attached for working ebuild and eclass.
Created attachment 832133 [details] Working ebuild for wxwidgets-3.2.1
(In reply to Vladislav Mikhailikov from comment #39) > Created attachment 832133 [details] > Working ebuild for wxwidgets-3.2.1 Thanks for your work, I needed it for cemu: https://github.com/cemu-project/Cemu. I only needed to update the wxwidgets eclass to be able to use it
note: kicad-7 (due out in the next few weeks) is almost wxgtk-3.2 dependant... https://gitlab.com/kicad/code/kicad/-/issues/13181
(In reply to jon R-B from comment #41) > note: kicad-7 (due out in the next few weeks) is almost wxgtk-3.2 > dependant... > > https://gitlab.com/kicad/code/kicad/-/issues/13181 It's nearly there at https://github.com/gentoo/gentoo/pull/28715. It's someone's recruitment task and it's essentially finished.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5fa6a7f4de2426217956f0a893c480b9fe873c2 commit b5fa6a7f4de2426217956f0a893c480b9fe873c2 Author: brahmajit das <listout@protonmail.com> AuthorDate: 2022-11-21 08:47:43 +0000 Commit: Arsen Arsenović <arsen@gentoo.org> CommitDate: 2023-01-20 22:15:47 +0000 x11-libs/wxGTK: Version bump to 3.2.1 Closes: https://bugs.gentoo.org/577030 Closes: https://bugs.gentoo.org/873124 Signed-off-by: brahmajit das <listout@protonmail.com> Signed-off-by: Arsen Arsenović <arsen@gentoo.org> x11-libs/wxGTK/Manifest | 2 + .../wxGTK/files/wxGTK-3.2.1-configure-tests.patch | 19 +++ .../wxGTK-3.2.1-gtk3-translation-domain.patch | 12 ++ x11-libs/wxGTK/wxGTK-3.2.1.ebuild | 177 +++++++++++++++++++++ 4 files changed, 210 insertions(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c31e7b31bee82014fe36ca695dc52c21dfe9f8da commit c31e7b31bee82014fe36ca695dc52c21dfe9f8da Author: brahmajit das <listout@protonmail.com> AuthorDate: 2022-11-21 19:24:20 +0000 Commit: Arsen Arsenović <arsen@gentoo.org> CommitDate: 2023-01-20 22:15:46 +0000 x11-libs/wxGTK: eclass preparation Closes: https://bugs.gentoo.org/577030#c37 Signed-off-by: brahmajit das <listout@protonmail.com> Closes: https://github.com/gentoo/gentoo/pull/28360 Signed-off-by: Arsen Arsenović <arsen@gentoo.org> eclass/wxwidgets.eclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=81b2fcc4ef99f828f27fc5d2621bd89f03ba6558 commit 81b2fcc4ef99f828f27fc5d2621bd89f03ba6558 Author: Maciej Barć <xgqt@gentoo.org> AuthorDate: 2023-01-20 23:10:39 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2023-01-20 23:19:54 +0000 app-misc/golly: bump to 4.2 Bug: https://bugs.gentoo.org/577030 Closes: https://bugs.gentoo.org/890330 Signed-off-by: Maciej Barć <xgqt@gentoo.org> app-misc/golly/Manifest | 1 + app-misc/golly/golly-4.2.ebuild | 70 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 71 insertions(+)
