General compiliation instructions for bzflag 1.7g0 and linux
- Fiberchunks
- Administrator
- Posts: 397
- Joined: Tue Dec 03, 2002 5:58 am
- Location: Groton, CT
General compiliation instructions for bzflag 1.7g0 and linux
Pick a way to install / build and stick with it...for right now, use the cvs method; here goes:
1. make a directory in your home directory called cvs (or whatever):
$mkdir cvs
2. cd into that directory:
$cd cvs
3. grab the sources from sourceforge:
$cvs -d:pserver:anonymous@cvs.bzflag.sourceforge.net:/cvsroot/bzflag login
Password: <just hit enter>
$cvs -z3 -d:pserver:anonymous@cvs.bzflag.sourceforge.net:/cvsroot/bzflag co -r v1_7 bzflag
4. stuff will happen (this is good), you are now populating the bzflag cvs directory with files...
5. cd into the new bzflag directory you have
$cd bzflag
6. issue the following commands:
$make linux
$make
--It will start compiling a bunch of things (bzfs, bzflag, etc...)...when this is all done, and if you have errors -- let me know, and we'll try again...
If, however, this completes sucessfully, you will now have a shiny new bin directory in the bzflag directory, which will contain bzflag, bzfs, bzfls, etc..
If this is the case (sucess), then from the bin directory, do:
$bzflag -directory ../data
If it runs, you can go back to the bzflag directory, and issue (as root):
#make install
and it should be kosher
Good luck, let me know if it works
Peace
1. make a directory in your home directory called cvs (or whatever):
$mkdir cvs
2. cd into that directory:
$cd cvs
3. grab the sources from sourceforge:
$cvs -d:pserver:anonymous@cvs.bzflag.sourceforge.net:/cvsroot/bzflag login
Password: <just hit enter>
$cvs -z3 -d:pserver:anonymous@cvs.bzflag.sourceforge.net:/cvsroot/bzflag co -r v1_7 bzflag
4. stuff will happen (this is good), you are now populating the bzflag cvs directory with files...
5. cd into the new bzflag directory you have
$cd bzflag
6. issue the following commands:
$make linux
$make
--It will start compiling a bunch of things (bzfs, bzflag, etc...)...when this is all done, and if you have errors -- let me know, and we'll try again...
If, however, this completes sucessfully, you will now have a shiny new bin directory in the bzflag directory, which will contain bzflag, bzfs, bzfls, etc..
If this is the case (sucess), then from the bin directory, do:
$bzflag -directory ../data
If it runs, you can go back to the bzflag directory, and issue (as root):
#make install
and it should be kosher
Good luck, let me know if it works
Peace
Error with missing GLU.h
If you're having problems...
Some distros (e.g. Mandrake) ship with a rather limited version of mesa, and will generate errors about a missing GLU.h file when you follow the above steps. If this is the case, go download the newest version of mesa from http://3dmesa.sourceforge.net and install it, then try compiling again (if you install a new version of mesa and are using nvidia's drivers, you'll have to reinstall them afterwards, too).
I've posted this several other places in response to problems over time, and told several people privately. Just thought it'd be a good idea to put here, since it occurs so frequently.
Some distros (e.g. Mandrake) ship with a rather limited version of mesa, and will generate errors about a missing GLU.h file when you follow the above steps. If this is the case, go download the newest version of mesa from http://3dmesa.sourceforge.net and install it, then try compiling again (if you install a new version of mesa and are using nvidia's drivers, you'll have to reinstall them afterwards, too).
I've posted this several other places in response to problems over time, and told several people privately. Just thought it'd be a good idea to put here, since it occurs so frequently.
I have e6 that was compiled (AFAICT) as a .deb specifically for the distro I use (version is "bzflag 1.7e6-xandros" - Xandros is the distro name, Debian based). I'm not a newbie to Linux - but there's a lot I still don't know, and I haven't done any work with CVS - so:
Question: does the CVS version have a different set of dependencies than the g0 version that is in unstable for Debian?
Figured I'd ask before I try I assume it would, but am keeping fingers crossed...
TIA
KR
Question: does the CVS version have a different set of dependencies than the g0 version that is in unstable for Debian?
Figured I'd ask before I try I assume it would, but am keeping fingers crossed...
TIA
KR
"My other tank is a sailboat..."
CVS and building on Mac OS X
For those of you that try these instructions on Mac OS X, after having just gone through the process myself, I figured I would share some thoughts.
The instructions are pretty much the same for Mac OS X except instead of "make linux", you'd normally do a "make macosx". Then proceed as usual.
For me, this process failed running 10.2.6 due to incorrect header inclusion ordering and some bogus defines. You'll end up with an error in one of the system header files (math.h) where several #define macros (in include/common.h) get in the way when MACOSX is defined (which the makefile does for you).
The "actual" problem is a little involved, but there is a simple minimal keystroke fix to get things to work: modify include/common.h and #include <math.h> right before all of the definitions for the floating point math routines.
There are even better solutions that would be more "correct", but that should get "most everything" to build. Something else will fail, but I believe the core targets that you'll care about get built.
BETTER YET, if you want to avoid that whole mess, there is a Project Builder project in src/platform that will build the current Mac OS X distribution for you with the click of a button..
Cheers!
The instructions are pretty much the same for Mac OS X except instead of "make linux", you'd normally do a "make macosx". Then proceed as usual.
For me, this process failed running 10.2.6 due to incorrect header inclusion ordering and some bogus defines. You'll end up with an error in one of the system header files (math.h) where several #define macros (in include/common.h) get in the way when MACOSX is defined (which the makefile does for you).
The "actual" problem is a little involved, but there is a simple minimal keystroke fix to get things to work: modify include/common.h and #include <math.h> right before all of the definitions for the floating point math routines.
There are even better solutions that would be more "correct", but that should get "most everything" to build. Something else will fail, but I believe the core targets that you'll care about get built.
BETTER YET, if you want to avoid that whole mess, there is a Project Builder project in src/platform that will build the current Mac OS X distribution for you with the click of a button..
Cheers!
-
- Private First Class
- Posts: 109
- Joined: Fri May 07, 2004 11:17 pm
- Contact:
dead thread
This thread is very old and should pretty much be considered dead. The information is partially out of date in any regard.
If you're building from CVS, it's random as to whether or not the XCode project will work or not. The ProjectBuilder project will not likely be maintained after 1.10.6. If you use the ProjectBuilder project in CVS on the v1_10branch, it should work just fine even now. 1.12 will most likely move over to the XCode project, though.
You don't need to be root to build no matter how you build, command-line or not.
Cheers!
p.s. Start a new thread for new questions.. this thread needs to die (and it may get moved into the attic anyways).
If you're building from CVS, it's random as to whether or not the XCode project will work or not. The ProjectBuilder project will not likely be maintained after 1.10.6. If you use the ProjectBuilder project in CVS on the v1_10branch, it should work just fine even now. 1.12 will most likely move over to the XCode project, though.
You don't need to be root to build no matter how you build, command-line or not.
Cheers!
p.s. Start a new thread for new questions.. this thread needs to die (and it may get moved into the attic anyways).
-
- Private First Class
- Posts: 109
- Joined: Fri May 07, 2004 11:17 pm
- Contact: