Test autopackage for Linux users

Test autopackage for Linux users - Printable Version

+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Project (https://www.vdrift.net/Forum/forumdisplay.php?fid=4)
+--- Forum: Development (https://www.vdrift.net/Forum/forumdisplay.php?fid=9)
+--- Thread: Test autopackage for Linux users (/showthread.php?tid=259)

Test autopackage for Linux users - thelusiv - 07-06-2006

If you're using VDrift on Linux please test this package. It is 142 MB downloaded, 192 MB installed. This will be the upcoming release of VDrift, unless someone finds some major fault.

Download: http://sqrville.org/vdrift-2006-07-06.x86.package
Delete your ~/.vdrift/ directory - make sure your settings are all cleared from previous versions

Code:
rm -Rf ~/.vdrift/
Delete any existing vdrift executables

Code:
sudo rm -f `whereis vdrift`
make sure you no longer have:
/usr/games/vdrift
/usr/bin/vdrift
/usr/games/bin/vdrift
Delete any existing vdrift data

Code:
sudo rm -Rf /usr/share/games/vdrift
if your data is somewhere else delete that too. make sure everything's gone.
Run the autopackage.
chmod +x vdrift-2006-07-06.x86.package
./vdrift-2006-07-06.x86.package
Enter your root password when prompted
Wait while it installs. It takes a while, and at times it may seem to be doing nothing. Why is there no progress bar for installing?
There is no desktop entry made yet, just type "vdrift" in a console. The game should run and work!

Re: Test autopackage for Linux users - FFuser - 07-06-2006

thelusiv Wrote:[*]Enter your root password when prompted

It should work without password too.

Quote:[*]Wait while it installs. It takes a while, and at times it may seem to be doing nothing. Why is there no progress bar for installing?

You can place a bug-report to auopacakage

Quote:[*]There is no desktop entry made yet, just type "vdrift" in a console. The game should run and work!

Maybe we should make it before release, could be very helpfull for some people.
If you didn't install it as root run '~/.local/share/games/vdrift/bin/vdrift'

- thelusiv - 07-06-2006

There's a new one up now at the same link as before, will get updated shortly with FFuser's additions of desktop entry, icon installation and language file installation fixes

- thelusiv - 07-06-2006

OK that one's no longer there

This is the last package I will make before release unless there are problems...I don't foretell any Smile

http://sqrville.org/vdrift-2006-07-06-minimal.x86.package

It is only 23 MB, let me know how it works for you...

autopackage issues - thelusiv - 07-07-2006

We've run into a little problem with the autopackage, this is the problem we've been having with OpenAL. In some older versions of OpenAL ALUT is included in the library, while in the newer versions ALUT is provided by a separate lib (freealut). On my system I'm building against the new AL and freealut, so if you have an older copy of AL the package won't work for you, and you'll have to compile with old_openal=1.

Another issue is that I can't use apg++ on my system (autopackage's compiler which does some magic to make it easier to loosely link) or I'll get the bouncing cars issue. So I'm using g++-3.4 to compile. This probably isn't the best solution for the autopackage.

Finally I think i18n support might be left out of the autopackage for this release to simplify things...

So the autopackage is working on my system (Debian etch), but not on a Gentoo system because portage still doesn't have freealut and the new openal.

Re: autopackage issues - FFuser - 07-07-2006

thelusiv Wrote:Another issue is that I can't use apg++ on my system (autopackage's compiler which does some magic to make it easier to loosely link) or I'll get the bouncing cars issue. So I'm using g++-3.4 to compile. This probably isn't the best solution for the autopackage.

apg++ uses the normal g++ compiler, but does it twice (with the versions you deinfe)
export APBUILD_CXX1=g++-3.2
export APBUILD_CXX2=g++-3.4
and than using ap_build=1 => compiled the package two times with two compilers and not g++-4

Re: autopackage issues - thelusiv - 07-07-2006

FFuser Wrote:apg++ uses the normal g++ compiler, but does it twice (with the versions you deinfe)
export APBUILD_CXX1=g++-3.2
export APBUILD_CXX2=g++-3.4
and than using ap_build=1 => compiled the package two times with two compilers and not g++-4

OOOhhh...Well that makes sense, now I get it. Is there a way we can set this up in the SConstruct so users don't have to mess with environment vars?

Re: autopackage issues - FFuser - 07-07-2006

thelusiv Wrote:
FFuser Wrote:apg++ uses the normal g++ compiler, but does it twice (with the versions you deinfe)
export APBUILD_CXX1=g++-3.2
export APBUILD_CXX2=g++-3.4
and than using ap_build=1 => compiled the package two times with two compilers and not g++-4
OOOhhh...Well that makes sense, now I get it. Is there a way we can set this up in the SConstruct so users don't have to mess with environment vars?

probably it can be integrated in SCons, but it hould be tried out (I can only install g++-3.4 and g++-3.2 so I can't test it)

- thelusiv - 07-08-2006

FFuser: Some of your i18n changes are giving me warnings:

scons src-package Wrote:scons: warning: Two different environments were specified for target guilists.cpp,
but they appear to have the same action: guilists_to_cppfile_builder(target, source, env)
File "po/SConscript", line 145, in i18n

scons: warning: Two different environments were specified for target optionslist.cpp,
but they appear to have the same action: options_to_cppfile_builder(target, source, env)
File "po/SConscript", line 146, in i18n

scons: warning: Two different environments were specified for target VDrift.pot,
but they appear to have the same action: pot_builder(target, source, env)
File "po/SConscript", line 147, in i18n

scons: warning: Two different environments were specified for target nl.mo,
but they appear to have the same action: mo_builder(target, source, env)
File "po/SConscript", line 156, in i18n

- thelusiv - 07-09-2006

All above links are no longer up, the new release is available...