Fs2 open on Linux/Acquiring the Code - Revision history

DAK at 06:05, 22 April 2025

2025-04-22T06:05:36Z

← Older revision		Revision as of 06:05, 22 April 2025
Line 64:		Line 64:
	<hr>		<hr>

	<h3>⚠️ ATTENTION</h3>		<h1>⚠️ ATTENTION</h1>
	<ul>		<ul>
	<li>Please clone the repository recursively. If not cloned recursively, the code may not compile on your machine.</li>		<li>Please clone the repository recursively. If not cloned recursively, the code may not compile on your machine.</li>

DAK: Guide to acquire the source code from GitHub

2025-04-22T06:04:58Z

Guide to acquire the source code from GitHub

@@ Line 7: / Line 7: @@
 {{Note| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary
 executable.}}
-Now get the source. Run from a terminal:
+This guide will walk the user through on how to acquire and download the source code locally to their machine.
- $ git clone https://github.com/scp-fs2open/fs2open.github.com.git
+<h1>For New Users</h1>
-This will pull in the most recent source code from the 'master' branch.
+This section of the code will explain on how to acquire the source code and download it to your system. For the sake of simplicity to new users, I am using Visual Studio Code to demonstrate on how to clone the source code.
-<br>
 [[Category:FreeSpace Open on Linux|Acquiring the Code]]

Echelon9: Reflect source code hosting via Git

2015-05-03T04:32:03Z

Reflect source code hosting via Git

← Older revision		Revision as of 04:32, 3 May 2015
Line 7:		Line 7:
	{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary		{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary
	executable.}}		executable.}}
	Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the ~~svn~~ command, this way git~~/svn~~ will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have git~~/svn~~ installed on your system. See the [[Fs2_open_on_Linux/Installing Git\|Installing Git]] chapter on installing Git.		Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the git command, this way git will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have git installed on your system. See the [[Fs2_open_on_Linux/Installing Git\|Installing Git]] chapter on installing Git.

	Now get the source. Run from a terminal:		Now get the source. Run from a terminal:
Line 13:		Line 13:
	$ git clone https://github.com/scp-fs2open/fs2open.github.com.git		$ git clone https://github.com/scp-fs2open/fs2open.github.com.git

	~~$ svn checkout svn://svn.icculus.org/fs2open/trunk/fs2_open (deprecated)~~		This will pull in the most recent source code from the 'master' branch.
	This will pull in the most recent source code from the 'master~~' or 'HEAD~~' branch.
	<br>		<br>

	[[Category:FreeSpace Open on Linux\|Acquiring the Code]]		[[Category:FreeSpace Open on Linux\|Acquiring the Code]]

Niffiwan at 23:28, 25 April 2015

2015-04-25T23:28:14Z

← Older revision		Revision as of 23:28, 25 April 2015
Line 7:		Line 7:
	{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary		{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary
	executable.}}		executable.}}
	Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the svn command, this way svn will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have svn installed on your system. See the [[Fs2_open_on_Linux/Installing ~~Subversion~~\|Installing ~~Subversion~~]] chapter on installing ~~Subversion~~.		Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the svn command, this way git/svn will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have git/svn installed on your system. See the [[Fs2_open_on_Linux/Installing Git\|Installing Git]] chapter on installing Git.

	Now get the source. Run from a terminal:		Now get the source. Run from a terminal:
	$ svn checkout svn://svn.icculus.org/fs2open/trunk/fs2_open
	This will pull in in the source code from the 'HEAD' branch.		$ git clone https://github.com/scp-fs2open/fs2open.github.com.git

			$ svn checkout svn://svn.icculus.org/fs2open/trunk/fs2_open (deprecated)
			This will pull in the most recent source code from the 'master' or 'HEAD' branch.
	<br>		<br>

	[[Category:FreeSpace Open on Linux\|Acquiring the Code]]		[[Category:FreeSpace Open on Linux\|Acquiring the Code]]

Chief1983: Bypass useless CVS script page

2011-05-20T20:13:52Z

Bypass useless CVS script page

← Older revision		Revision as of 20:13, 20 May 2011
Line 3:		Line 3:
	CurrentPage=Acquiring the Code\|Acquiring the Code\|		CurrentPage=Acquiring the Code\|Acquiring the Code\|
	PrevPage=[[Fs2_open on Linux/Installing the Development Libraries\|Installing the Development Libraries]]\|		PrevPage=[[Fs2_open on Linux/Installing the Development Libraries\|Installing the Development Libraries]]\|
	NextPage=[[~~Fs2_open~~ on Linux/~~Checkout Script~~\|~~Checkout Script~~]]}}		NextPage=[[Fs2 open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]}}
	<p></p>		<p></p>
	{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary		{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary

TopAce at 18:13, 24 September 2008

2008-09-24T18:13:02Z

← Older revision		Revision as of 18:13, 24 September 2008
Line 13:		Line 13:
	This will pull in in the source code from the 'HEAD' branch.		This will pull in in the source code from the 'HEAD' branch.
	<br>		<br>

			[[Category:FreeSpace Open on Linux\|Acquiring the Code]]

R00b at 19:07, 22 June 2008

2008-06-22T19:07:46Z

← Older revision		Revision as of 19:07, 22 June 2008
Line 10:		Line 10:

	Now get the source. Run from a terminal:		Now get the source. Run from a terminal:
	$ svn://svn.icculus.org/fs2open/trunk/fs2_open		$ svn checkout svn://svn.icculus.org/fs2open/trunk/fs2_open
	This will pull in in the source code from the 'HEAD' branch.		This will pull in in the source code from the 'HEAD' branch.
	<br>		<br>

Ni1s: cvs becomes subversion

2008-05-14T17:50:54Z

cvs becomes subversion

← Older revision		Revision as of 17:50, 14 May 2008
Line 7:		Line 7:
	{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary		{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary
	executable.}}		executable.}}
	Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the ~~CVS~~ command, this way ~~CVS~~ will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have ~~CVS~~ installed on your system. See the [[Fs2_open_on_Linux/Installing ~~CVS~~\|Installing ~~CVS~~]] chapter on installing ~~CVS~~.		Before you begin, make sure you have write permissions on your current working directory. $HOME/$USER is a pretty safe bet. I recommend that you create a permanent /$HOME/$USER/src directory from which you run the svn command, this way svn will only update the files changed the next time you download the source and it's always nice to have things organized. Make sure you have svn installed on your system. See the [[Fs2_open_on_Linux/Installing Subversion\|Installing Subversion]] chapter on installing Subversion.

	Now get the source. Run from a terminal:		Now get the source. Run from a terminal:
	$ ~~cvs -d:pserver:anonymous:anonymous@warpcore.org~~:/~~home~~/~~fs2source/cvsroot login~~		$ svn://svn.icculus.org/fs2open/trunk/fs2_open
	~~This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore~~.~~org's CVS repository "/home/fs2source/cvsroot" and login.~~		This will pull in in the source code from the 'HEAD' branch.
	~~<br><br>~~
	~~Next, get the code from the server we just connected to, either from the development branch:~~
	~~$ cvs -z3 -d:pserver:anonymous@warpcore~~.org:/~~home~~/~~fs2source~~/~~cvsroot co~~ fs2_open
	~~..or from the "stable branch":~~
	~~$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open~~
	~~{{Note\| For just playing the game it is usually best to get~~ the code from the ~~"stable branch", as it will generally be more.. stable.}}~~
	~~Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open", either from the default branch (the development branch -~~ HEAD~~) or from the branch determined by the "-r" option. In the latter checkout we specified the~~ branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.
	<br>		<br>

Castor: spelling

2007-10-27T10:02:58Z

spelling

← Older revision		Revision as of 10:02, 27 October 2007
Line 18:		Line 18:
	$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open		$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
	{{Note\| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}		{{Note\| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
	Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open"~~. Either~~ from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option. In the latter checkout we specified the branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.		Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open", either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option. In the latter checkout we specified the branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.
	<br>		<br>

Castor: Stable branch clarifications

2007-10-27T09:59:41Z

Stable branch clarifications

← Older revision		Revision as of 09:59, 27 October 2007
Line 11:		Line 11:
	Now get the source. Run from a terminal:		Now get the source. Run from a terminal:
	$ cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login		$ cvs -d:pserver:anonymous:anonymous@warpcore.org:/home/fs2source/cvsroot login
	This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.<br><br>		This tells the CVS tool to first use a password file for authentication (pserver), that you are user "anonymous" with the password "anonymous" who wants to access warpcore.org's CVS repository "/home/fs2source/cvsroot" and login.
			<br><br>
	Next, get the code from the server we just connected to, either from the development branch:		Next, get the code from the server we just connected to, either from the development branch:
	$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open		$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co fs2_open
	..or from the "stable branch" ~~(currently 3.6.9)~~:		..or from the "stable branch":
	$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open		$ cvs -z3 -d:pserver:anonymous@warpcore.org:/home/fs2source/cvsroot co -r fs2_open_3_6_9 fs2_open
	{{Note\| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}		{{Note\| For just playing the game it is usually best to get the code from the "stable branch", as it will generally be more.. stable.}}
	Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option.		Both of the last two commands tell the CVS server that we want to checkout (co) the CVS module "fs2_open". Either from the default branch (the development branch - HEAD) or from the branch determined by the "-r" option. In the latter checkout we specified the branch "fs2_open_3_6_9" (implying the release 3.6.9 of FS2 Open), but this naming is only due to "historical reasons" - release specific branches don't exist at the time being, we will get the most recent stable code available by using that checkout.
	<br>		<br>