-- [ Picked text/plain from multipart/alternative ] A quick Q. What game should I put in for the srcds -game paramenter? Hopefully so I can just download the needed files and not all the extra files that come with it.
On 7/25/05, Slash <[EMAIL PROTECTED]> wrote: > > Your Makefile is messed up. First, GAME_DIR is the location of your > Steam SRCDC installation directory. That's where the "tier0_i486.so, > etc" are. So you need the SRCDS installed on the computer you are > compiling on, basically (I suppose you could just get the .so files in > question from somewhere, but I'm not sure). . > > If those files are located, for example, > /usr/local/games/steam/srcds/bin/(tier0_i486.so,vstdlib_i486.so), your > Makefile should read like this: > > GAME_DIR=/usr/local/games/steam/srcds > > That will fix those No such file or directory errors (note: don't add > the bin/ directory to that line, as commands later on append bin/ > automatically). Your CPP_LIB line is weird. Is that spread over 2 > lines? Verify its all on the same line. If you are using pico or nano > or something it could be wordwrapping. And I guess both those files > are in the same directory for you (on my systems they are in different > places)? > > For the GCC/G++/etc yours are probably correct, you can make sure by > typing "which gcc" and "which g++", etc in a console. It tells you the > path of where these files are. In fact, this will work too (note those > are backticks, not quotes. It tells the computer to execute the > command contained within and put the result there): > > CC=`which gcc` > CPLUS=`which g++` > CLINK=`which gcc` > > Make sure your Xerces paths are correct as well. XERCES_INC_DIR / > XERCES_LIB_DIR. If you installed it manually, then its hard to say > where you put it. But chances are you will get errors relating to > xerces if you set it incorrectly. > > If you try compiling again and get this error: > > "./vcpm: error while loading shared libraries: tier0_i486.so: cannot > open shared object file: No such file or directory" > > Do this: > > export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. > > This adds the current directory to the paths of where to look for > libraries (ie, the .so files in question). Note that there is a > colon(:) and period (.) at the end there. Very important since . > represents the current directory. > > -Slash > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > -- - Ben Davison - http://www.shadow-phoenix.com -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
