Packaging and installation?
by Markus Nuebel · in Torque Game Engine · 09/13/2004 (2:26 am) · 2 replies
Hi guys.
I recently ported our game to Linux.
Since I am new to Linux I would like to know, how the complete game should be distributed.
For Win32 we have an installer, that installs the game executable, the scripts, the game content, OpenAL/opengl2d3d/glu2d3d libs and then places a shortcut on the desktop.
- Do I have to distribute third party libs like OpenAL for Linux? (It's not like placing a dll in the game directory as for Win32)
- Do I have to package all the game content and executable as an rpm?
- Is there a free installer, that helps with doing Linux installations?
Thanks.
-- Markus
I recently ported our game to Linux.
Since I am new to Linux I would like to know, how the complete game should be distributed.
For Win32 we have an installer, that installs the game executable, the scripts, the game content, OpenAL/opengl2d3d/glu2d3d libs and then places a shortcut on the desktop.
- Do I have to distribute third party libs like OpenAL for Linux? (It's not like placing a dll in the game directory as for Win32)
- Do I have to package all the game content and executable as an rpm?
- Is there a free installer, that helps with doing Linux installations?
Thanks.
-- Markus
About the author
#2
I never thought of installing the Linux TorqueDemo, to checkout the setup. Great advise.
Yes it's a Torque based game.
I will get lokisetup an play with it a bit.
Thanks.
09/14/2004 (1:36 am)
Hey thanks Alexander.I never thought of installing the Linux TorqueDemo, to checkout the setup. Great advise.
Yes it's a Torque based game.
I will get lokisetup an play with it a bit.
Thanks.
Torque 3D Owner abc
abc
There is a installer tool called, lokisetup I think (many linux games uses it).
btw, is it a torque game?
If so, you have all you need I think.
And also, you said "It's not like placing a dll in the game directory as for Win32"... you are only partly right there.
You can place the "dll" (.so) in the game directory and then create a startup script that fixes the LD_LIBRARY_PATH variable so that the system finds that "dll" (if you have torque, check runtorque.sh).
One final note, don't use rpm because not all linux distributions uses that format.