x86_64 Linux Sauerbraten build

by enigma_0Z on 11/18/2006 20:52, 10 messages, last message: 11/21/2006 03:28, 2539 views, last view: 05/05/2024 10:39

Hi all,

I've built an x86_64 Linux binary of sauerbraten, as well as modified the sauerbraten_unix script to include it. You can find the file here:

http://sledgehammer.ath.cx/files/sauer_64.tgz

Just "cd" to the directory that you extracted sauerbraten, and run "tar xvzf /path/to/download/sauer_64.tgz". Run sauerbraten_unix and enjoy.

Aard: I can build x86_64 binaries for future releases if you would like me to.

   Board Index   

#1: ..

by Drakas on 11/18/2006 22:39

Note that this build is not anyhow affiliated with Aard or anyone else who makes the engine. The file size of the server looks twice as big as it should do and the client file looks about 200 KB bigger.

Just to let you know, people can cross-compile for other platforms. And also, most Linux users should compile Sauerbraten for themselves, if the architecture is not available!

reply to this message

#2: ..

by enigma_0Z on 11/18/2006 23:51

Yeah, forgot to say that. Thanks.

And yes I know that people can cross-compile themselves, but alot of linux users do not have or want all of the devel libs necessary to build a program. I do software development, so it is conveinant for me. Just trying to contribute.

reply to this message

#3: Re: ..

by Drakas on 11/19/2006 11:29, refers to #2

Thats a good thing :)

Thanks!

reply to this message

#4: ..

by Grogan on 11/19/2006 19:41

"The file size of the server looks twice as big as it should do and the client file looks about 200 KB bigger."

The binaries are not stripped. That accounts for a significant increase in size on disk. (symbols... they don't actually cause the program to use more memory though)

reply to this message

#5: Re: ..

by Drakas on 11/19/2006 20:58, refers to #4

Did I say anything about memory?

reply to this message

#6: ..

by Grogan on 11/19/2006 23:39

No, but I did for the benefit of those who might not know any better.

reply to this message

#7: Re: ..

by enigma_0Z on 11/20/2006 22:47, refers to #4

Is there any advantage to stripping (or not stripping) the binaries, and how/should I?

reply to this message

#8: Stripping Binaries

by Morosoph on 11/21/2006 02:24

A quick Google finds this:

http://www.linuxfromscratch.org/hints/downloads/files/small-lfs.txt

Setting the environment variable CC to "gcc -s"
will cause gcc to strip binaries as they are created.

Looking at the Makefile in sauerbraten/src, you could edit CXXFLAGS to include a -s option. I didn't bother when compiling Sauerbraten for my Opteron.

The advantage in stripping the binaries is simply that the code takes less disk space. The disadvantage is that any debugger you wish to use to analyse flaws in the code will not have a full set of debugging symbols with which to work.

reply to this message

#9: Re: Stripping Binaries

by MeatROme on 11/21/2006 02:44, refers to #8

also look at the last two lines of Makefile ... the ones calling "strip" :)

reply to this message

#10: Ah yes...

by Morosoph on 11/21/2006 03:28

Um. I never saw those.

Yeah. A make install should do it! Doh!

reply to this message

   Board Index