 |
Hm, thanks for the heads up. :) Though I'm a bit confused about how to solve this? I didn't specify a specific wxWidgets version in DarkRadiant's sources, or did I? |
 |
You did it implicitly: By using development dependencies at: debian/control: Build-Depends: *-dev So automatically setting development version at: m4/wxwin.m4: wx_requested_micro_version :D ;) |
|
|
I can see that debian/control contains the following line: Build-Depends: debhelper (>= 5), autotools-dev, libgtkmm-2.4-dev, libgtkglextmm-x11-1.2-dev, libxml2-dev, libglew-dev, libboost-regex-dev, libboost-filesystem-dev, libboost-serialization-dev, libboost-test-dev, libboost-python-dev, python-dev, libvorbis-dev, libopenal-dev, libalut-dev, libjpeg-dev, libftgl-dev, libwxbase3.0-dev, libwxgtk3.0-dev I guess you're referring to libwxgtk3.0-dev? I guess you have to enlighten me a bit, as I don't recognise the connection yet. How is libwxgtk3.0-dev automatically causing a request of the unreleased 3.0.5 version? The automake M4 macro you're mentioning is used by the configure.ac script, but it is only requiring 3.0.0 or higher: configure.ac:119 WX_CONFIG_CHECK([3.0.0], [wxWin=1], [wxWin=0], [std,gl,stc]) |
|
|
Sorry, I think that wasn't true. As "-dev" doesn't mean "development version" as in my distro, but "development package". And version is 3.0.4 on Debian Sid nowadays: https://packages.debian.org/sid/libwxgtk3.0-dev But, as I said, most likely that version is implicitly informed elsewhere than in your code. |
|
|
You're on Arch, aren't you? Is it possible that some PKGBUILD script on your system has been pulling the 3.0.5 tag from the wxWidgets repository? I recently built DR successfully on an Arch Anywhere installation, and it worked with the wxgtk dependencies just fine. Btw, there's a PKGBUILD script already contained in the root folder of DarkRadiant's git repo. Doesn't this work for you? |
|
|
Running darkradiant from Debian Stable doesn't exhibit the issue: On Stable: darkradiant (2.6.0-3+b1) libwxgtk3.0-dev (3.0.4+dfsg-8) On Unstable: darkradiant (2.7.0-1) libwxgtk3.0-dev (3.0.4+dfsg-14) |
|
|
I will test the PKGBUILD... |
|
|
Sorry, I just noticed that the PKGBUILD in DarkRadiant's root folder is already referring to the imminent DR 2.8.0 release, the tag doesn't exist yet. You'll have to switch the versions in that file to 2.7.0: git+https://github.com/codereader/DarkRadiant.git#tag=2.7.0 |
|
|
This is the one I used, but with Debian unstable: https://gitlab.com/es20490446e/express-repository/-/blob/master/Packages/darkradiant/PKGBUILD |
|
|
Is it a good idea to derive the pacman dependencies from the WIKI by parsing the HTML output string? This can easily go wrong. Why not just add it to the PKGBUILD directly? |
|
|
It can go wrong if your build system isn't able to inform about those errors before publishing the package. But if it does getting the info directly from the source warrants that it's up to date, and correct, at any given time. Without human supervision. https://i.imgur.com/E5yUge2.gif |
|
|
Well, as far as I can see there's not much I can do about the problem you're experiencing, so I'll set this issue to acknowledged for the time being. When you find the source of the issue, let me know if there's anything within the DR sources that needs to be changed. |
|
|
The PKGBUILD on GitHub fails to build: https://bin.privacytools.io/?4fdeac53aed7952f#cPS1HgHA+8BF7L9FrXR93q3Ja7JoHMRntNFK8ctqDUo= |
|
|
Did you install the boost package? |
|
|
That worked. |
- Anonymous
