windows source
windows source
where do I access the updated windows source to compile with mingw
????????
thanks
????????
thanks
same as you do for any source code. Get it out of CVS. It is all the same source.
www.bzflag.org -> cvs access link on the left hand side.
www.bzflag.org -> cvs access link on the left hand side.
JeffM
- Saturos
- Art Master General
- Posts: 1111
- Joined: Mon Apr 19, 2004 2:48 pm
- Location: Berlin/Germany
- Contact:
A tipp: The forum has a search-feature.
You could try to search the boards for the answers to your questions instead of creating 28094046 topics per day...
You could try to search the boards for the answers to your questions instead of creating 28094046 topics per day...
Saturos ([phagozytose] : www.phago.de)
should I quit the forums if you can't stand me that much
EDIT: read old post, man this was a dumb response...
EDIT: read old post, man this was a dumb response...
Last edited by Winny on Tue Jun 20, 2006 3:05 am, edited 1 time in total.
there is a full guide on exactly how to get CVS on the CVS access page that is linked on the www.bzflag.org mainpage.
just read it.
just read it.
JeffM
if it keeps asking you, then you have not done it correctly.
you must do it as 2 lines, just like this
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bzflag login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bzflag co -P bzflag
make sure you use bzflag for the module name.
you will also probably want to add -r v2_0branch after the -P part, so you get the 2.0.x compatable code, not the 2.1.x code.
you must do it as 2 lines, just like this
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bzflag login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bzflag co -P bzflag
make sure you use bzflag for the module name.
you will also probably want to add -r v2_0branch after the -P part, so you get the 2.0.x compatable code, not the 2.1.x code.
JeffM
as has been said in many other places here, no 2.1.x is NOT compatable with 2.0.x. And will be incompatble with itself as the protocll changes as new features are added.
if it was compatable it would still be 2.0.x. The version numbers do mean something.
Basicly compatable version have the same second number. We change that number when the code becomes incompatable.
2.1.x is development for 2.2.0, then next "big" version. What we have been doing with 2.0.2, 2.0.4, etcc. has just been making revisions of the 2.0.0 line. That is why they are are all 2.0.something
there is a nice big sicky post about what all the version numbers mean here
http://my.bzflag.org/bb/viewtopic.php?t=1043
in the Game Releases and Versions forum.
if it was compatable it would still be 2.0.x. The version numbers do mean something.
Basicly compatable version have the same second number. We change that number when the code becomes incompatable.
2.1.x is development for 2.2.0, then next "big" version. What we have been doing with 2.0.2, 2.0.4, etcc. has just been making revisions of the 2.0.0 line. That is why they are are all 2.0.something
there is a nice big sicky post about what all the version numbers mean here
http://my.bzflag.org/bb/viewtopic.php?t=1043
in the Game Releases and Versions forum.
JeffM