Getting Started with Development - Revision history

Zonkmachine: /* Debugging */ fix gdb command

2023-09-02T10:05:29Z

‎Debugging: fix gdb command

2021-01-16T16:00:36Z

2020-12-09T18:56:01Z

‎Code editing

2014-12-01T21:55:33Z

link do code::blocks

2014-07-01T07:20:16Z

‎Debugging

2014-01-15T14:11:32Z

+linkup to "Coding_Conventions" page

2014-01-15T14:01:59Z

+linkup to "Coding_Conventions" page

2013-08-18T00:24:39Z

2013-01-25T13:38:02Z

‎Getting the Code

2013-01-25T13:33:47Z

Scrap notes about how to build; point to COMPILING.txt in the repository instead

@@ Line 22: / Line 22: @@
 For developers on Linux, gdb can be used for debugging
-  gdb ./src/pioneer
+  gdb ./build/pioneer
   run
 This starts pioneer in gdb. After a crash, you can get a back trace by typing into the gdb prompt "bt". Bugs, and feature requests, should be logged on the issue tracker.
 === Code editing ===

← Older revision		Revision as of 16:00, 16 January 2021
Line 30:		Line 30:
	=== Code editing ===		=== Code editing ===
	Most development is done on GNU/Linux machines, although there are some developers using MS Visual Studio on Windows.		Most development is done on GNU/Linux machines, although there are some developers using MS Visual Studio on Windows.
		+
		+
		+	=== Misc. ===
		+	[https://www.samueltaylor.org/articles/how-to-learn-a-codebase.html How to learn a codebase]

← Older revision		Revision as of 18:56, 9 December 2020
Line 29:		Line 29:

	=== Code editing ===		=== Code editing ===
−	Most development is done on GNU/Linux machines, although there are ~~Microsoft Visual Studio compability. An alternative to~~ MS Visual Studio ~~is [[Building with Code::Blocks]]~~.	+	Most development is done on GNU/Linux machines, although there are some developers using MS Visual Studio on Windows.

← Older revision		Revision as of 21:55, 1 December 2014
Line 26:		Line 26:

	This starts pioneer in gdb. After a crash, you can get a back trace by typing into the gdb prompt "bt". Bugs, and feature requests, should be logged on the issue tracker.		This starts pioneer in gdb. After a crash, you can get a back trace by typing into the gdb prompt "bt". Bugs, and feature requests, should be logged on the issue tracker.
		+
		+
		+	=== Code editing ===
		+	Most development is done on GNU/Linux machines, although there are Microsoft Visual Studio compability. An alternative to MS Visual Studio is [[Building with Code::Blocks]].

← Older revision		Revision as of 07:20, 1 July 2014
Line 25:		Line 25:
	run		run

−	Bugs, and feature requests, should be logged on the issue tracker.	+	This starts pioneer in gdb. After a crash, you can get a back trace by typing into the gdb prompt "bt". Bugs, and feature requests, should be logged on the issue tracker.

@@ Line 10: / Line 10: @@
 ===Coding Conventions===
 see [[Coding_Conventions]]
 ==Compiling==
@@ Line 16: / Line 15: @@
 [https://github.com/pioneerspacesim/pioneer/blob/master/COMPILING.txt COMPILING.txt]
 ===Debugging===

@@ Line 7: / Line 7: @@
 You may also need to clone the [https://github.com/pioneerspacesim/pioneer-thirdparty pioneer-thirdparty] repository, depending on what platform you're on. It is needed to build on Windows. You should clone this in a directory ''next to'' your clone of the pioneer directory (''not'' a sub-directory). Further instructions are in the COMPILING.txt file (linked below).
 ==Compiling==
 There are instructions for how to compile the code included in the repository:
@@ Line 15: / Line 18: @@
 ===Debugging===
 For developers on Linux, gdb can be used for debugging

@@ Line 4: / Line 4: @@
   git clone git://github.com/pioneerspacesim/pioneer.git
-This will get you on the "master" branch, which is where new code is merged. This is the latest and greatest development and is quite unstable. To build a specific alpha, you need to checkout the appropriate release tag:
+This will get you on the "master" branch, which is where new code is merged. This is the latest and greatest development. It should be stable.
 You may also need to clone the [https://github.com/pioneerspacesim/pioneer-thirdparty pioneer-thirdparty] repository, depending on what platform you're on. It is needed to build on Windows. You should clone this in a directory ''next to'' your clone of the pioneer directory (''not'' a sub-directory). Further instructions are in the COMPILING.txt file (linked below).

@@ Line 6: / Line 6: @@
 This will get you on the "master" branch, which is where new code is merged. This is the latest and greatest development and is quite unstable. To build a specific alpha, you need to checkout the appropriate release tag:
-  git checkout alpha20
+  git checkout alpha30
 ==Compiling==