Package Details: slade 3.2.7-10

Git Clone URL: https://aur.archlinux.org/slade.git (read-only, click to copy)
Package Base: slade
Description: SLADE3 Doom editor
Upstream URL: http://slade.mancubus.net/
Licenses: GPL
Submitter: grubber
Maintainer: envolution
Last Packager: envolution
Votes: 33
Popularity: 0.052678
First Submitted: 2011-08-16 11:58 (UTC)
Last Updated: 2025-03-30 17:54 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

envolution commented on 2025-03-05 20:36 (UTC) (edited on 2025-03-05 20:36 (UTC) by envolution)

@kinker31 I suggest extra/rebuild-detector to help you determine what packages need recompilation as your libraries will change and packages compiled for previous versions will need to be properly linked to function appropriately.

@sh-5.2$ ldd `which slade3.bin` | grep -i flac
        libFLAC.so.14 => /usr/lib/libFLAC.so.14 (0x00007dd0e1c12000)
@sh-5.2$ pacman -Qo /usr/lib/libFLAC.so.14
/usr/lib/libFLAC.so.14 is owned by flac 1.5.0-1

based on your report, you need to rebuild slade without a cached copy

kinker31 commented on 2025-03-02 04:40 (UTC)

Neither the stable or git versions of Slade seem to work recently; Probing a slight bit on what I got when I ran it through the terminal, the culprit seems to be that the flac libraries Slade uses are far outdated, requesting libFLAC.so.12 when the current version is libFLAC.so.15.

Potential downgrade options for the package only go as far back as libFLAC.so.13, and downgrading the sfml package such that it doesn't segfault immediately when opening any sound/music lumps is already a risk as is.

Retro_Gamer commented on 2025-01-07 05:16 (UTC) (edited on 2025-01-07 05:17 (UTC) by Retro_Gamer)

@envolution: Yes, that seems to have gotten it sorted, your AUR is now making a working build again. Thank you much.

envolution commented on 2025-01-04 20:53 (UTC)

@Retro_Gamer thanks for your report, I think I've resolved the issue if you're interested to try it again

Retro_Gamer commented on 2025-01-04 17:12 (UTC) (edited on 2025-01-04 17:17 (UTC) by Retro_Gamer)

This AUR build no longer works, it does build seemly fine but when ran only throws this error before quitting :

slade: symbol lookup error: slade: undefined symbol: _ZNK13wxGLCanvasEGL15IsShownOnScreenEv

Following Slade's own build instructions works fine though.

git clone https://github.com/sirjuddington/SLADE.git
cd SLADE/dist
cmake ..
make
sudo make install

Somehow the way this AUR PKGBUILD is now doing it isn't working, but it used to.

envolution commented on 2025-01-03 18:18 (UTC)

pkgrel 7 builds wxwidgets into the /usr/share/slade3 directory and patches the slade binary to use it instead of the system wxwidgets-gtk. This way we can be sure external packages are not affected by slade's current requirements.

Compile times will be about twice as long. It's not pretty, but I'm hoping this is just a temporary slade issue.

Please flag if there is an issue with this build, I don't have a workflow to trigger the fault personally so am relying on you guys to tell me if it needs more work.

kinker31 commented on 2025-01-03 08:48 (UTC)

Attempting to run Slade directly through the terminal causes a segmentation fault or a similar error, giving me slade: symbol lookup error: slade: undefined symbol: _ZNK13wxGLCanvasEGL15IsShownOnScreenEv as a response.

However, I can still run the program just fine with the new package, and I'm happy to report the TEXTUREx editor finally works.

kinker31 commented on 2025-01-03 04:57 (UTC)

Update on the TEXTUREx issue: Turns out the problem doesn't lie in the package itself, more in the wxWidgets version used to build the thing. Long story short, wxWidgets needs to be custom-built for SLADE, using the wxUSE_GLCANVAS_EGL flag I thought was meant for the project itself. Should it work here, it should also work on the git version, which bears the same issue.

Also, on a semi-related note, when you update to the new version, you'll probably have to custom-build SFML too based on 2.6, 3.0 causes Slade to crash as well. Here's the relevant Github post on this issue.