TGE 1.4.2 Tarball

#1 Uh
well

gbriggs@falcor:/tmp/chunky/t1.4.2/torque$ make -f mk/configure.mk BUILD=RELEASE OS=LINUX COMPILER=GCC3; make
<lots of snippage>
--> Linking out.GCC3.RELEASE/torqueDemo.bin
../lib/xiph/linux/libogg.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
make[1]: *** [out.GCC3.RELEASE/torqueDemo.bin] Error 1
make: *** [default] Error 2
gbriggs@falcor:/tmp/chunky/t1.4.2/torque$

That's as it is in CVS right now.

Alternatively, here's one I linked against my own build stuff:

gbriggs@falcor:/tmp/chunky/t1.4.2/torque/example$ ldd ./torqueDemo.bin 
        libogg.so.0 => /usr/local/lib/libogg.so.0 (0x4002f000)
        libvorbis.so.0 => /usr/local/lib/libvorbis.so.0 (0x40034000)
        libtheora.so.0 => /usr/local/lib/libtheora.so.0 (0x4005c000)
        libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x40081000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x400ff000)
        libdl.so.2 => /lib/libdl.so.2 (0x40151000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x40155000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40167000)
        libm.so.6 => /lib/libm.so.6 (0x4021f000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x40242000)
        libc.so.6 => /lib/libc.so.6 (0x4024a000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40367000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40431000)
        /lib/ld-linux.so.2 (0x40000000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x40440000)
        libfontconfig.so.1 => /usr/X11R6/lib/libfontconfig.so.1 (0x40448000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4046f000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4048f000)
        libz.so.1 => /usr/lib/libz.so.1 (0x404f9000)
gbriggs@falcor:/tmp/chunky/t1.4.2/torque/example$ cat /etc/slackware-version 
Slackware 10.1.0
gbriggs@falcor:/tmp/chunky/t1.4.2/torque/example$ gcc --version
gcc (GCC) 3.3.4

Here's the binary [just gzipped]: icculus.org/~chunky/stuff/torqueDemo.bin.gz

Gary (-;

#2 Ok...will this work for the demo?

www.rustycode.com/matt/TorqueDemoLinux-1-4-2.zip

I worry about not having a way to set the executable as having an execute property since this isn't supported by the Windows file system.

If this doesn't work for you guys, could you please use this .zip as a basis to build a working version that I can upload to the product page? You can also reference anything you need from the current demo. Please email/yousendit/post it so that I can get to it.

I am going to be needing a similar pass on the TGE 1.5 demo/sdk sometime next week and will need a hand if we are going to be able to launch it with a Linux version.

What do you guys feel about having or not having an executable in the SDK tarball? I know generally most Linux users are pretty comfortable with compiling their own exectuables (or operating systems ;). Let me know what you think.

Once we have the demo working, I can get with that person to get a secured download/upload for getting the SDK tarball ready also.

Thanks guys! Your support is what is keeping Linux alive for TGE!

#3 You forgot the /lib directory.
Therefore the sound doesn't work.
Don't need an executable in the sdk tarball and we don't need an installer.

#4 I agree with David. For Linux SDK distro is fine to have just sources/libs. No installer or compiled binary (executable) really needed. tar.gz is more than enough imo

#5 @Matt:
I also agree with David and bank about not needing executables in the SDK installation download. I also really don't much like installers for things like the SDK as they tend to put icons and junk on my desktop I don't want. For a demo, I don't mind an installer and would agree it adds a touch to the "finished" feel of the demo for the end user.

As far as TorqueDemoLinux-1-4-2.zip, it ran fine on my system (SuSE 10.0), however:

1) You aren't including the lib/xiph/linux/lib* files. These should probably be in a lib/ sub-directory in the .zip file.
2) If the lib/ sub-directory is included, you should have a sh script to launch (mostly to modify LD_LIBRARY_PATH to catch the libs delivered).
3) If this is the linux demo, you don't need the .bat and .command files.
4) The root of the .zip file is the example directory. You might want to put all the files in a TorqueDemoLinux-1.4.2 directory and then create the .zip file so the only thing in the .zip's root directory is the TorqueDemoLinux-1.4.2 directory.

The original 1.4.2-RC1 installer, TorqueGameEngineSDK-1.4.2-RC1.bin, installed uncorrupted libraries if you need a good source for the libs.

I made a new .zip file with the changes above as well as setting the execute bits on both runtorque.sh and torqueDemo.bin. I'm uploading it now to my web directory. Download it from TorqueDemoLinx-1.4.2-ZAZ.zip. Email me or reply to this thread if you would though once you've retrieved it so I can remove it as its taking up 19M of my whopping 27M of space, :-).

Do with it what you want, including ignore it, just let me know when you're done with it so I can remove it.

Quote:Thanks guys! Your support is what is keeping Linux alive for TGE!

Thanks for the saying this. It gives me some hope and motivation and I'm sure others also, although it does tend to emphasize how precarious the support for TGE on linux has become.

I'd be happy to help with the 1.5 pass also if I'm available, although I'm in and out of town a bit this week.

#6 Matt,

I would make yah an installer etc, but do not have linux setup anymore. Lost my dual boot HDD and now running on a 20GB'er and money is tight due to my midical issues earlier in the year. Doubt I will get another HDD any time soon.

Willing to walk something through doing a build/installer just need your (GG's) blessing to send that person the license file for the installer software.

-Ron

#7 Todd,
Thanks for repackaging it for me. I figured there would be issues like that but I don't have a Linux install anywhere to test on. I went ahead and grabbed the .zip you made so you can free up that space. If I don't hear differently from the rest of the Linux users, I will post that as the "official" Linux build (probably sometime tomorrow).

Ron,
Now worries man =) Thanks for all of the help you have given us over the last year! I'll let you know if I need a hand getting someone else to build an installer.

#8 @Matt:
Thanks for grabbing it and replying so quickly. I did do a few quick tests here locally on my machine, but it'd be good if you could make that available for a few other eyes to check it out too.

BTW, I can understand the issues with man power and equipment in regard to linux support. For something simple like this though, i.e. execute bit being set, building and minor types of testing, vmplayer might offer a free and convenient solution. I'd be happy to setup or help setup a, say an ubuntu, virtual machine for GG to use if you are interested in something like this.

@Ron:
Check your gmail box in case your notify and that are different addresses.

#9 Zaz,

Thanks for donating a 40GB drive! I will be sure to use it for LINUX only and get back to the TGE duties that I have sorely neglected the past month +


-Ron

#10 @Ron:
Hehe, and I went to all the trouble to offer it to you privately via email, :-).

No problem, like I said, consider partial payment for the contributions you've already made to TGE-L. I'll get it in the mail about the middle of the week as tomorrow I'm moving my dad from the hospital to his apartment ... for about the umpteenth time this year.

#11 You guys can reach the updated version provided by Todd here:

www.rustycode.com/matt/TorqueDemoLinux-1.4.2-ZAZ.zip

Check it out (quickly =) before I post it to the product page!

#12

Quote:You forgot the /lib directory.
Therefore the sound doesn't work.

Speaking of sound. I have a clean install of Fedora Core 5, and sound doesn't work. I did look for the OpenAL library on openal.org, but that seems to be some ancient version (0.8 ?) that also doesn't work.

How do I get sound to work on Linux?

(Also: OpenAL seems to hang the system once you've started/stopped the game 40-60 times on Windows -- perhaps it's time to use some alternative method to play sound?)

#13 Just in case you needed any more confirmation; Linux developers will be more than happy with just a tarball, with no compiled binary stuffs in it. If they need something that can be considered a golden binary executable they could always download the demo. Please don't wrap it in an installer, I hate installers.


I'd actually also suggest that a long term goal for a lot of library problems is to distribute the source code for the libraries with the rest of the code, have the build process independantly build a static library [with a flag to allow someone to link dynamically], and link with that. That'll fix all your LD_LIBRARY_PATH problems, /lib/ problems, and those specific CVS binary problems.

Smart developers drinking the modern SCM kool-aid [or the more traditional flavor here] can use Vendor branches under their own steam if they wish to remain independantly up to date. the CVS vendor branch technique. Torque is tidily laid out so they can do this with remarkable ease.

Because this isn't a linux forum post without some bashing: In the name of all that is good, please don't use the misnomer that is sourcesafe, but it works for "vendor branches" too.


This does not violate the LGPL. By having the abililty to dynamically link if you set a different flag, you also make it trivial for developers to satiate the terms of the lgpl. A developer can distribute both a static [read LGPL section 5 & 6a] and dynamically linked [LGPL section 6b] version of their software in the same package, and only officially support the static version.

Gary (-;

#14 Oh, ow. k, I just loaded up the zip file [stupid slow internet connections. I typed out that whole last post while it was downloading :-/].

gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$ ls -l lib
total 4648
-rw-r--r--  1 gbriggs users  359800 2004-04-20 21:27 libSDL-1.2.so.0
-rw-r--r--  1 gbriggs users   16256 2006-05-28 11:55 libogg.so
-rw-r--r--  1 gbriggs users   16256 2006-05-28 11:55 libogg.so.0
-rw-r--r--  1 gbriggs users   16256 2006-05-28 11:55 libogg.so.0.5.2
-rw-r--r--  1 gbriggs users  246416 2005-12-14 17:29 libopenal.so
-rw-r--r--  1 gbriggs users  123492 2006-05-28 11:55 libtheora.so
-rw-r--r--  1 gbriggs users  123492 2006-05-28 11:55 libtheora.so.0
-rw-r--r--  1 gbriggs users  123492 2006-05-28 11:55 libtheora.so.0.1.0
-rw-r--r--  1 gbriggs users  159884 2006-05-28 11:55 libvorbis.so
-rw-r--r--  1 gbriggs users  159884 2006-05-28 11:55 libvorbis.so.0
-rw-r--r--  1 gbriggs users  159884 2006-05-28 11:55 libvorbis.so.0.3.0
-rw-r--r--  1 gbriggs users 1030564 2006-05-28 11:55 libvorbisenc.so
-rw-r--r--  1 gbriggs users 1030564 2006-05-28 11:55 libvorbisenc.so.0
-rw-r--r--  1 gbriggs users 1030564 2006-05-28 11:55 libvorbisenc.so.2.0.0
-rw-r--r--  1 gbriggs users   27596 2006-05-28 11:55 libvorbisfile.so
-rw-r--r--  1 gbriggs users   27596 2006-05-28 11:55 libvorbisfile.so.0
-rw-r--r--  1 gbriggs users   27596 2006-05-28 11:55 libvorbisfile.so.3.1.0
gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$ du -sh lib
4.6M    lib
gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$

Ouch. Hit torqueDemo.bin with ldd and you'll see that it is specifically loading the .so.0 version of each. Traditionally the whole *purpose* of the .so and the .so.0 are to be symlinks to the real version. If they're not symlinks, then you're better off leaving them out altogether.

Other stuff I'd forgotten:
1) It's a demo. Strip it.

gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$ ls -l torqueDemo.bin 
-rwxr-xr-x  1 gbriggs users 5034866 2006-10-06 14:46 torqueDemo.bin*
gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$ strip torqueDemo.bin 
gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$ ls -l torqueDemo.bin 
-rwxr-xr-x  1 gbriggs users 4063784 2006-10-09 17:40 torqueDemo.bin*
gbriggs@falcor:/tmp/chunky/TorqueDemoLinux-1.4.2$

There goes a meg of binary junk.

2) Top line of runetorque.sh: "#!/bin/sh -x"

ewwww debugging info. *snip snip*.


Mmm. I think that was about it that stood out immediately.

TorqueDemoLinux-1.4.2-chks.zip. It's only a meg smaller than the ZAZ one, but... well, there you have it.

Gary (-;

#15 So is everyone agreed that I should go with Gary's build?

#16 Oh, and reading back:

Quote:I have a clean install of Fedora Core 5, and sound doesn't work.

Does sound not work for anything? Your mixers are probably set to zero as is the default with a couple of the sound subsystems. Just open up your generic sound panel of choice and crank them up a little.

If sound still isn't working, you probably need to go into your distribution's system control panel and set up the actual device; tell it the specific card you have.

Sorry if that's a little vague, I haven't got an FC5 box on hand at the moment [stupid QA people here roasted the box :-(]

Gary (-;

#17 Hey Guys,
The current linux installer of tge openal wont work in FedoraCore 5
Gary's is ok but it lacks the openal binary,
Todd's is ok but the openal binary dont work in FedoraCore 5 or Suse10.1(opensuse.org) here.
The openal binary in the current installer doesn't work in FedoraCore 5 or Suse10.1(opensuse.org) here.
Thats running both via the runtorque.sh
I used my openal binary (from Suse rpm install) in FC5 with both above zip demos and it works fine
I have uploaded it to here if it helps.

Also
I agree about NOT having the executables in the Source down and it be in archive format instead of an installer