Compiling Doomseeker on Linux: Difference between revisions

Line 29: Line 29:
* zlib ''(optional - possibly static)''
* zlib ''(optional - possibly static)''
* libbzip2 ''(optional - possibly static)''
* libbzip2 ''(optional - possibly static)''
* mercurial ''(needed in order to clone repository)''
* mercurial ''(needed in order to download the source)''


Install the following as root/superuser:
Install the following as root/superuser:
Line 114: Line 114:
</pre>
</pre>


=== Current stable version ===
=== Current release version ===
Show the current stable version:
Show the current release version:
<pre>
<pre>
cd "$HOME"/doomseeker_build/doomseeker && \
cd "$HOME"/doomseeker_build/doomseeker && \
Line 121: Line 121:
</pre>
</pre>


If you want to compile the current stable version, run the following:
If you want to compile the current release version, run the following:
<pre>
<pre>
cd "$HOME"/doomseeker_build/doomseeker && \
cd "$HOME"/doomseeker_build/doomseeker && \
Line 128: Line 128:
and [[#Compiling|compile]].
and [[#Compiling|compile]].


After compiling and backing up the current stable version, run the following:
After compiling and [[#Backup|backing up]] the current release version, run the following:
<pre>
<pre>
cd "$HOME"/doomseeker_build/doomseeker && \
cd "$HOME"/doomseeker_build/doomseeker && \
hg update
hg update default
</pre>
</pre>


Line 239: Line 239:
</pre>
</pre>


Now GDB should have you in its own command prompt. You probably want to log the output, so lets output to a file doomseekerdebug.log:
Now gdb should have you in its own command prompt. You probably want to log the output, so lets output to a file doomseekerdebug.log:
<pre>
<pre>
(gdb) set logging on doomseekerdebug.log
(gdb) set logging on doomseekerdebug.log
Line 260: Line 260:
All output will be copied into the doomseekerdebug.log, which can then be scrutinized later, or perhaps posted to the [http://zandronum.com/tracker/ Bug Tracker] for other developers to look at.
All output will be copied into the doomseekerdebug.log, which can then be scrutinized later, or perhaps posted to the [http://zandronum.com/tracker/ Bug Tracker] for other developers to look at.


To exit GDB's command prompt, use "quit", "q" or Ctrl-D:
To exit gdb's command prompt, use "quit", "q" or Ctrl-D:
<pre>
<pre>
(gdb) quit
(gdb) quit
20

edits