Back to the Vavoom Forum Archives


Forum

Improved Vavoom Documentation

Sun, 05 Aug 2007 13:31:28

skyhawk

This is a request, directed to Janis, that some serious consideration be given to expanding and clarifying the installation notes packaged with the Vavoom source code tarballs. My computer is running Mandriva 2007.0, kernel 2.6.17-5mdv. I want to install Vavoom-1.24. I quote below from the installation notes provided with vavoom-1.24.tar.gz: =============================================== (BEGIN QUOTED TEXT) 3.2 Linux/UNIX installation =============================================== In order to compile and run Vavoom under Linux, you need the following: Compiler and tools: * GNU C++ Compiler, GNU make (every LINUX user must have them) Libraries: * zlib (<!-- m --><a class="postlink" href="http://www.zlib.net">http://www.zlib.net</a><!-- m -->) * libpng (<!-- m --><a class="postlink" href="http://www.libpng.org">http://www.libpng.org</a><!-- m -->) * libjpeg (<!-- m --><a class="postlink" href="http://www.ijg.org">http://www.ijg.org</a><!-- m -->) * Allegro 4.0 (<!-- m --><a class="postlink" href="http://alleg.sourceforge.net">http://alleg.sourceforge.net</a><!-- m -->) or * SDL 1.2 (<!-- m --><a class="postlink" href="http://www.libsdl.org">http://www.libsdl.org</a><!-- m -->) and SDL_mixer 1.2 (<!-- m --><a class="postlink" href="http://www.libsdl.org/projects/SDL_mixer/">http://www.libsdl.org/projects/SDL_mixer/</a><!-- m -->). * OpenGL: OpenGL implementation from your video card's manufacturer or MESA (<!-- m --><a class="postlink" href="http://www.mesa3d.org">http://www.mesa3d.org</a><!-- m -->) and X-Windows development libraries. * AllegroGL (<!-- m --><a class="postlink" href="http://allegrogl.sourceforge.net">http://allegrogl.sourceforge.net</a><!-- m -->) if you want to use OpenGL with Allegro driver. Optional: * OpenAL (<!-- m --><a class="postlink" href="http://www.openal.org">http://www.openal.org</a><!-- m -->), the source must be checked out from the CVS repository. You will find info on this on OpenAL website or at Creative developer centre (<!-- m --><a class="postlink" href="http://developer.creative.com">http://developer.creative.com</a><!-- m -->). * libvorbis (<!-- m --><a class="postlink" href="http://www.vorbis.com">http://www.vorbis.com</a><!-- m -->) * libmad (<!-- m --><a class="postlink" href="http://www.underbit.com/products/mad/">http://www.underbit.com/products/mad/</a><!-- m -->) * mikmod (<!-- m --><a class="postlink" href="http://mikmod.raphnet.net/">http://mikmod.raphnet.net/</a><!-- m -->) * FLAC (<!-- m --><a class="postlink" href="http://flac.sourceforge.net/">http://flac.sourceforge.net/</a><!-- m -->) And of course the Vavoom sources. =============================================== (END QUOTED TEXT) 3.2 Linux/UNIX installation =============================================== Specifically, I want to compile the source code using SDL 1.2. I have the SDL 1.2 run-time libraries installed, but I have already discovered that I need the development files included in libSDL1.2-devel-1.2.11-3mdv2007.0.i586.rpm. When I attempt to install that rpm, I get the following list of failed dependencies: [me@mycomputer archive]$ rpm -ivh libSDL1.2-devel-1.2.11-3mdv2007.0.i586.rpm error: Failed dependencies: devel(libaa) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libaudio) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libdirect-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libdirectfb-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libfusion-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgg) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libggi) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgii) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgpm) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libslang) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 All of this is not covered, or even hinted at, in the installation notes. I am also expecting that, if I begin satisfying these failed dependencies, I will find additional failed dependencies. So, I could begin to feel as if I am trapped in an endless loop. I am a very patient and persistent fellow, however, so I have little doubt that I will be able to see the installation process through to the end. A word of warning in the documentation might be appropriate, though, for those individuals who are easily frustrated. Vavoom does not seem to be a very active topic in some of the popular Linux forums, so I am wondering if installation difficulties have prevented it from rising to the top of the list of Linux game engines. I would like to see some clarification as to the advantages, if any, of downloading and installing the optional components mentioned in the Vavoom documentation, specifically: * OpenAL (<!-- m --><a class="postlink" href="http://www.openal.org">http://www.openal.org</a><!-- m -->), the source must be checked out from the CVS repository. You will find info on this on OpenAL website or at Creative developer centre (<!-- m --><a class="postlink" href="http://developer.creative.com">http://developer.creative.com</a><!-- m -->). * libvorbis (<!-- m --><a class="postlink" href="http://www.vorbis.com">http://www.vorbis.com</a><!-- m -->) * libmad (<!-- m --><a class="postlink" href="http://www.underbit.com/products/mad/">http://www.underbit.com/products/mad/</a><!-- m -->) * mikmod (<!-- m --><a class="postlink" href="http://mikmod.raphnet.net/">http://mikmod.raphnet.net/</a><!-- m -->) * FLAC (<!-- m --><a class="postlink" href="http://flac.sourceforge.net/">http://flac.sourceforge.net/</a><!-- m -->) My present intent is to compile the Vavoom source code with SDL 1.2 and OpenGL. According to the documentation, the following parameters are available when the configuration script is run: --prefix=PATH - specify prefix of installation. Default is /usr/local --with-allegro - use Allegro for hardware API. This is the default. --with-sdl - use SDL for hardware API. --without-opengl - compile without OpenGL support. --without-openal - compile without OpenAL support. Thus, my configuration script should read (maybe): ./configure --with-sdl --without-openal Correct me if I am wrong on this. Also, let me (and others) know if it might be simpler to compile with Allegro, rather than SDL 1.2. It looks like I might be able to avoid a lot of failed dependencies by choosing Allegro. Vavoom is a very ambitious project. The screenshots I have seen of Vavoom in action are impressive, and I definitely do not want to retrograde by using DOSemu to run Doom, Heretic, and Hexen. From what I have read, my Nvidia TNT2 Pro graphics card should be adequate to handle the game engine in 2D-accelerated mode, which is all I can manage with the OpenGL driver.
Mon, 06 Aug 2007 16:10:41

Janis Legzdinsh

As I understand, it's the first time you are installing something by compiling it from source code.
Specifically, I want to compile the source code using SDL 1.2. I have the SDL 1.2 run-time libraries installed, but I have already discovered that I need the development files included in libSDL1.2-devel-1.2.11-3mdv2007.0.i586.rpm. When I attempt to install that rpm, I get the following list of failed dependencies: [me@mycomputer archive]$ rpm -ivh libSDL1.2-devel-1.2.11-3mdv2007.0.i586.rpm error: Failed dependencies: devel(libaa) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libaudio) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libdirect-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libdirectfb-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libfusion-0.9) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgg) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libggi) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgii) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libgpm) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586 devel(libslang) is needed by libSDL1.2-devel-1.2.11-3mdv2007.0.i586
In order to compile it, you'll have to install them. Development packages shouldn't have more dependencies than corresponding binary packages. Also they should be quite small.
All of this is not covered, or even hinted at, in the installation notes.
It assumes you have some experience in compiling from sources.
I am also expecting that, if I begin satisfying these failed dependencies, I will find additional failed dependencies.
libSDL shouldn't have many dependencies. When you select it in Mandrake control centre it will show you all of the dependencies.
A word of warning in the documentation might be appropriate, though, for those individuals who are easily frustrated.
Good point.
I would like to see some clarification as to the advantages, if any, of downloading and installing the optional components mentioned in the Vavoom documentation
* OpenAL - enables 3D sound driver. It should give you more realistic sound. * libvorbis - support for music in Ogg Vorbis format. * libmad - support for music in MP3 format. * mikmod - support for music in various tracker style formats. * FLAC - support for sounds in FLAC format (it's a compressed sound format). Some of the user made levels may use sounds and music in these formats, so having them is highly recommended.
Thus, my configuration script should read (maybe): ./configure --with-sdl --without-openal Correct me if I am wrong on this.
That will be correct one.
Also, let me (and others) know if it might be simpler to compile with Allegro, rather than SDL 1.2. It looks like I might be able to avoid a lot of failed dependencies by choosing Allegro.
I don't think there will be much difference in dependencies.
Tue, 07 Aug 2007 13:06:53

skyhawk

Thanks very much for your prompt reply. It looks like I now have all the information I need to do the Vavoom installation. I am very new to Linux, but I have already compiled programs. Vavoom is simply a little more complex than the installations I have done, and I would like the best chance possible of getting it right the first time. I also should mention that I am a college graduate with a B.A. degree in chemistry, so if documentation is somewhat unclear to me, I am sure it must be to many others. Vavoom is a great concept. I hope to follow its progress as new versions are released.
Wed, 08 Aug 2007 20:43:55

scen

Hello skyhawk, welcome to hell <!-- s:twisted: --><img src="{SMILIES_PATH}/icon_twisted.gif" alt=":twisted:" title="Twisted Evil" /><!-- s:twisted: --> Don't be afraid to ask any question, and feel free to report any bug/problem that you may notice during your Vavoom fragging sessions! <!-- s8) --><img src="{SMILIES_PATH}/icon_cool.gif" alt="8)" title="Cool" /><!-- s8) -->

Back to the Vavoom Forum Archives