PlaneShift
Support => Technical Help: Problems BEFORE entering the game => Topic started by: Zorium on April 17, 2004, 06:23:02 am
-
I downloaded the linux installation from sourceforge then gunzipped the file. When I untarred it about 20 megs of file was missing!!!!! :O. The file which was missing was hydlaa.zip which seems to be key to installation. When I tried to open the file there was nothing in it and when I copied it there was nothing there. Any idea on how to work around this? (or you could send me the file :P)
-
After reading several different posts on installation of planeshift on linux i\'ve decided my problems stem from not doing things right :) anyway is it possible to install planeshift using the binary download of crystal space and avoiding cvs and other such messy command line things.
-
Installed everything as instructed by cvs but when I type ./psclient I get the following message; \"Please set CEL enviroment var!\" any ideas on how to fix this?
-
If you have really read the other threads you would know the answer :P
If it wants you to set the CEL export, then set it to the location where CEL is.
-
when I type
export CRYSTAL=$HOME/molblue/CS
then:
export CEL=$HOME/molblue/cel
and run the psclient I get the following error:
./psclient: line 52: src/client/psclient: No such file or directory
any ideas?
-
Hmm... interesting... your psclient file seems to be a shell script, but I wonder why? Mine is a binary like it should be... Can you post the contents of your psclient file?
-
This is the full contents of the file:
#!/bin/sh
# automake always builds programs inside the dir with source files
# but you have to start the programs from the top PS dir, so that they can find
# the sources. This scripts helps starting the progs and helps reminding people
#try to setup links to the plugins
if [ ! -f configure.ac ]; then
echo Please start this script from planeshift root dir
exit 1
fi
#link plugins to actual dir, so that planeshift will be able to find them
PLUGINS=\"src/client/gui/.libs/psgui src/server/database/dummy/.libs/dbdummy \\
src/server/database/mysql/.libs/dbmysql \\
src/common/psbehave/.libs/psbehave src/client/sound/.libs/pssound \\
src/common/psprop/imp/.libs/pflinearmovement \\
src/common/psprop/character/.libs/pfcharacterdata \\
src/common/psprop/npc/.libs/pfnpcdialog \\
src/common/psprop/proxlist/.libs/pfproximitylist \\
src/client/admin/.libs/psadmin\"
for i in $PLUGINS; do
#echo \"linking plugin $i\"
if [ -f $i.so ]; then
ln -s $i.so . >& /dev/null
fi
if [ -f $i.dll ]; then
#win32 can\'t symlink so we have to copy :(
cp $i.dll .
fi
done
#link CEL plugins... oh that\'s ugly...
if test -z \"$CEL\"; then
echo \"Please set CEL environment var!\"
exit 1
fi
for i in $CEL/*.so; do
if test -f $i; then
ln -s $i . >& /dev/null
fi
done
for i in $CEL/*.dll; do
if test -f $i; then
cp $i .
fi
done
SELF=`basename $0`
if test $SELF = \"psclient\"; then
src/client/psclient $@
fi
if test $SELF = \"psserver\"; then
src/server/psserver $@
fi
-
Hmm, which version of PS are you using? The package from the website or the CVS build? I\'m not sure but I think the package had such a script. The psclient script can\'t find the executable. Did you use make to build PS? I dont\' know where it creates the files since I use jam which places the compiled files in the /out/linuxx86/ folder and copies them over to the Planeshift root folder. Maybe make places the files in the /src/ folder but doesn\'t copy them over to the root dir since psclientalready exists or is write protected. I\'m not sure about this. Can you tell the steps you did to compile PS?
-
I mainly followed the cvs guide with a couple of exceptions:
I used make on CS instead of jam (the path trickt didn\'t work),
I also downloaded the new art directly from the website (actually the one used in the cvs guide but I thought i\'d mention it)
-
Why don\'t you use jam to build the sources? Make is deprecated with CS and PS afaik. And CEL doesn\'t support make at all I think.
-
Redid the ENTIRE thing and still got the same problem (I still used make on CS but jam didn\'t work so I had no choice :P)
-
Of course jam works. Just the make install doesn\'t work to install the binaries to your path. Just copy it to /usr/bin as root and it works :)
BTW: did you build CEL at all?
-
Ah I obviously didn\'t make myself clear jam works just not with CS (doesn\'t compile properly), everything was compiled with jam so I do have cel. Might just bite the bullet and redo it again on a different computer (faster too), with any luck i\'ll post the news of my success (though quite possibly the lack thereof) later today.
-
*bangs his head against the next available wall* Sorry i didn\'t get it what you said.*sigh* For CS: there is a bug in the source, that\'s why it doesn\'t compile completely. Look at some other similiar threads, I think the solution is somewhere. If in doubt, do a jam -a on CS and then do a jam again and post the output, so I can see the errors.
-
Doesn\'t work on my other computer by the way :(
Do you want me to post the entire output from jam -a and jam or just the last couple of lines or something (just checking because the entire output is well over 100 lines)
-
Just do a jam -a. When it is finished, do a jam without options and post the output. It will contain only the errors.
-
Did a jam -a (properly this time) then a jam and a none of them produced a single error that I could see but planeshift still doesn\'t work (didn\'t really expect it too but oh well).
EDIT: I\'ll put the output of ./pssetup -verbose and see if that helps
Warning: Failed to load `vfs\'; reason(s):
/usr/local/crystal/lib/vfs.so: File not found
./vfs.so: File not found
/home/root/molblue/planeshift/vfs.so: File not found
Warning: Failed to load `vfs\'; reason(s):
/usr/local/crystal/lib/vfs.so: File not found
/usr/local/crystal/lib/libvfs.so: File not found
./vfs.so: File not found
./libvfs.so: File not found
/home/root/molblue/planeshift/vfs.so: File not found
/home/root/molblue/planeshift/libvfs.so: File not found
WARNING: could not load plugin \'crystalspace.kernel.vfs\'
Couldn\'t load vfs plugin!
Warning: Failed to load `vfs\'; reason(s):
/usr/local/crystal/lib/vfs.so: File not found
./vfs.so: File not found
/home/root/molblue/planeshift/vfs.so: File not found
Warning: Failed to load `vfs\'; reason(s):
/usr/local/crystal/lib/vfs.so: File not found
/usr/local/crystal/lib/libvfs.so: File not found
./vfs.so: File not found
./libvfs.so: File not found
/home/root/molblue/planeshift/vfs.so: File not found
/home/root/molblue/planeshift/libvfs.so: File not found
WARNING: could not load plugin \'crystalspace.kernel.vfs\'
Warning: Failed to load `csfont\'; reason(s):
/usr/local/crystal/lib/csfont.so: File not found
./csfont.so: File not found
/home/root/molblue/planeshift/csfont.so: File not found
Warning: Failed to load `csfont\'; reason(s):
/usr/local/crystal/lib/csfont.so: File not found
/usr/local/crystal/lib/libcsfont.so: File not found
./csfont.so: File not found
./libcsfont.so: File not found
/home/root/molblue/planeshift/csfont.so: File not found
/home/root/molblue/planeshift/libcsfont.so: File not found
WARNING: could not load plugin \'crystalspace.font.server.default\'
Warning: Failed to load `soft3d\'; reason(s):
/usr/local/crystal/lib/soft3d.so: File not found
./soft3d.so: File not found
/home/root/molblue/planeshift/soft3d.so: File not found
Warning: Failed to load `soft3d\'; reason(s):
/usr/local/crystal/lib/soft3d.so: File not found
/usr/local/crystal/lib/libsoft3d.so: File not found
./soft3d.so: File not found
./libsoft3d.so: File not found
/home/root/molblue/planeshift/soft3d.so: File not found
/home/root/molblue/planeshift/libsoft3d.so: File not found
WARNING: could not load plugin \'crystalspace.graphics3d.software\'
Warning: Failed to load `imgplex\'; reason(s):
/usr/local/crystal/lib/imgplex.so: File not found
./imgplex.so: File not found
/home/root/molblue/planeshift/imgplex.so: File not found
Warning: Failed to load `imgplex\'; reason(s):
/usr/local/crystal/lib/imgplex.so: File not found
/usr/local/crystal/lib/libimgplex.so: File not found
./imgplex.so: File not found
./libimgplex.so: File not found
/home/root/molblue/planeshift/imgplex.so: File not found
/home/root/molblue/planeshift/libimgplex.so: File not found
WARNING: could not load plugin \'crystalspace.graphic.image.io.multiplex\'
Warning: Failed to load `aws\'; reason(s):
/usr/local/crystal/lib/aws.so: File not found
./aws.so: File not found
/home/root/molblue/planeshift/aws.so: File not found
Warning: Failed to load `aws\'; reason(s):
/usr/local/crystal/lib/aws.so: File not found
/usr/local/crystal/lib/libaws.so: File not found
./aws.so: File not found
./libaws.so: File not found
/home/root/molblue/planeshift/aws.so: File not found
/home/root/molblue/planeshift/libaws.so: File not found
WARNING: could not load plugin \'crystalspace.window.alternatemanager\'
Couldn\'t load iGraphics3D plugin!
Error initializing system!
Doesn\'t look too healthy...
-
Originally posted by Karosh_Steinkatz
If in doubt, do a jam -a on CS and then do a jam again and post the output, so I can see the errors.
This time you didn\'t get what what I said :P I told you to do it on Crystal Space, not on Planeshift ;) But for the Errors: either your CS was only half built (which I can\'t imagine) or you did not set your CRYSTAL export corectly.
-
Nope your bad again :P I did do it on Crystal Space just put the pssetup information there as an after thought (probably didn\'t make things very clear sorry).
So how should I got about setting these exports up correctly (full instructions so it can\'t :) go wrong.
-
No, I guess this is my bad again... *sigh* Note to self: thinking at 4am in the morning doesn\'t work well.
Let\'s say your copy of CS is in /opt/CS, CEL is in /opt/cel and PS is in /opt/planeshift. Now set your exports to:
export CRYSTAL=/opt/CS
export CEL=/opt/cel/
export CSCONFPATH=/opt/cel/
If you want to make a startup script go to /opt/planeshift and create a file with the exports in it. Add as the last line:
./psclient
and save it as client or whatever you like. Make it executable with
chmod +x client
Now when you want to play PS go to /opt/planeshift and type ./client
You can do it for the pssetup too, just change the last line of the file and save it as setup for example.
If it still doesn\'t work correctly, come back again ;)
Alternatively we can sit this out via ICQ, MSN or AIM.
-
Well it kind of worked. ./pssetup now works but ./psclient does not :( still get the same error so not much luck there.
-
Hmm, psclient seems to be missing something... can you do a ./psclient -verbose?
-
./psclient -verbose doesn\'t do anything :(. Just went ./configure in planeshift and it said crystal space could not be found, maybe this is causing the problem... (why I didn\'t notice this before is beyond me).
-
Got it working!!!!!! I modified the client file to do ./configure then jam (that actually didn\'t work but then I changed jam to jam -a). I then just changed the client file back to run psclient and it worked! :):):)