build instructions don't work #206
Comments
|
Hi @coreybruce! Are you currently building on |
|
Hey @Jammyjamjamman thanks for the reply, no sorry I was building from the current zipped stable, should I try cloning this and switching to the developer branch or try master first? |
|
Oh sorry, jumped the gun a bit and forgot to ask if you were using git at all I'd recommend trying to clone this repo + build the Some extra info about that error your getting: |
|
I got it to complete cmake after installing the dependencies needed and figured out it needed wxgtk2 not wxgtk3 (wxwidgets on debian/Ubuntu) might need to add the Arch dependencies as a couple of them are named differently and still don't know why Debian and Ubuntu based distros name packages so wierdly.. but I ran into this issue when I was building |
|
Hm I don't know what's gone wrong here I'm afraid. Googling shows that function is in the header Something that might help is, rather than building using cmake directly, is to use the scripts in mk/linux: |
|
This will be an issue (the "multiple definition of") when compiling with GCC 10+, due to a change in GCC 10 to default to You can see an example of what I did for Solus here [2]. In this example, you can see that as part of our packaging tooling, in our environment section I am effectively exporting our CFLAGS and LDFLAGS with the values mentioned above appended to the end. [1] https://gcc.gnu.org/gcc-10/porting_to.html |
|
Hi @JoshStrobl! Thanks for the help. This was already fixed in commit 5a35205 . Actually, looking at that error again, I don't know why this error would happen. Because I don't think this code has been changed since the release, where it did build. Maybe a full rebuild would fix the problem (delete the folder |
I just ran into this problem too, on Manjaro. As @Jammyjamjamman mentioned, it has to do with the algorithm include apparently. I added I had first removed the build directory but that didn't help. |
I'll have to reverse myself a little. It's not working now. I got a complete binary, but when it runs, the window is black, doesn't change, and it crashes in less than a minute with a lot of errors in the console. I'm attaching the console output |
|
Looks like some progress way made by smarter people than me :P |
|
I got the binary to run properly. I had to install ftgl. |
|
So.. yeah, looks like setupBuilddeps.sh needs updating. Here's the output of So really.. that seems more of a pacman bug. Same thing with the libcurl-gnutls dependency. Not installed and pacman didn't install it. |
|
Nice catch @andy5995! I suspect the real problem is pacman fails to install the packages because it can't find wxgtk (and doesn't fail gracefully). @coreybruce I'd suggest running the command below. If it succeeds, then try a clean build (of development branch) again: sudo pacman -S gcc-multilib cmake libcurl-gnutls sdl2 openal lua libjpeg-turbo libpng freetype2 wxgtk-common cppunit fribidi ftgl glew libogg libvorbis miniupnpc libircclient vlc libxml2 libx11 mesa gluI've removed |
|
I will give it a try and get back to you |
|
@Jammyjamjamman imo, cmake should exit with a fail code if it can't find ftgl. |
Fixes bugs found in iss #206. Building without FTGL fails and the error is confusing. So we'll fail at the cmake stage (suggested by andy5995). People who don't want it can disable this at their own peril! ;-)
Installed all of those exept gcc-multilib as Manjaro arm64 does not have this package and only supports 64bit arm but I am still getting cmake errors sadly. |
|
Thanks @coreybruce . Still the same error as before? If there's cmake errors, sounds like it's failing earlier. |
Hi there I tried to build the game from source using the build instructions from the website but ran into this issue.
I am building on Manjaro Arm64
So I looked at the Arch pkgbuild file as a reference and tried their cmake instructions but ran into some issues so this is the cmake argument I used to get it working in the root build folder instead of build in /mx/linux/build
I got cmake to work but when I tried to build I ran into this issue
The text was updated successfully, but these errors were encountered: