Jump to content

Compiling Doomseeker on Linux: Difference between revisions

(Created page with "'''Open a terminal and copy and paste the whole code box for each step.''' == Notes == If you received the error: '''pulling from https://bitbucket.org/Blzut3/doomseeker'''...")
 
Line 8: Line 8:
'''abort: HTTP Error 503: Repository Unavailable'''
'''abort: HTTP Error 503: Repository Unavailable'''


edit "$HOME"/doomseeker_build/doomseeker/.hg/hgrc file and change the default path
edit "$HOME"/doomseeker_build/doomseeker/.hg/hgrc file and change the default path:
<pre>
<pre>
[paths]
[paths]
Line 21: Line 21:


== Prerequisites ==
== Prerequisites ==
Doomseeker requires some development files in order to compile.
Doomseeker requires some tools and development files in order to compile:
* gcc - C and C++ compilers
* gcc - C and C++ compilers
* make
* make
Line 31: Line 31:
* mercurial ''(needed in order to clone repository)''
* mercurial ''(needed in order to clone repository)''


Install the following dependencies and tools as superuser:
Install the following as root/superuser:


=== Debian/Ubuntu ===
=== Debian/Ubuntu ===
Line 152: Line 152:
<pre>
<pre>
cd "$HOME"/doomseeker_build && \
cd "$HOME"/doomseeker_build && \
COPYANDPASTEDS="$(date +%Y%m%d%H%M)" && \
COPYANDPASTEDS="$(date +'%Y%m%d-%H%M')" && \
mkdir -pv "$COPYANDPASTEDS" && \
mkdir -pv "$COPYANDPASTEDS" && \
cp -rv doomseeker/build/{doomseeker,libwadseeker.so,engines} \
cp -rv doomseeker/build/{doomseeker,libwadseeker.so,engines} \
Line 159: Line 159:


If you did "Backup" or "Backup (Optional)", the previous files should be located at:
If you did "Backup" or "Backup (Optional)", the previous files should be located at:
: '''/home/<your username>/doomseeker_build/'''
: '''/home/<your username>/doomseeker_build/<your newly created directory>'''


== Updating ==
== Updating ==
Line 171: Line 171:


== Installation ==
== Installation ==
'''The following steps contain commands that require to be run as superuser with the sudo command.'''
'''The following steps have commands that require to be run as superuser with the sudo command.'''


If you want to install Doomseeker, do the following:
If you want to install Doomseeker, do the following:
Line 219: Line 219:
* [http://www.gnu.org/software/gdb/ gdb]
* [http://www.gnu.org/software/gdb/ gdb]


In most cases it is good idea to generate a back trace when Doomseeker crashes.
In most cases it is good idea to generate a backtrace when Doomseeker crashes.


Make debug directory.
Make debug directory:
<pre>
<pre>
mkdir -pv "$HOME"/doomseeker_build/doomseeker/debug
mkdir -pv "$HOME"/doomseeker_build/doomseeker/debug
</pre>
</pre>


Make a debug build of doomseeker.
Make a debug build of Doomseeker:
<pre>
<pre>
cd "$HOME"/doomseeker_build/doomseeker/debug && \
cd "$HOME"/doomseeker_build/doomseeker/debug && \
Line 234: Line 234:
</pre>
</pre>


You should now be able to use gdb to generate a back trace.
You should now be able to use gdb to generate a backtrace:
<pre>
<pre>
gdb doomseeker
gdb doomseeker
</pre>
</pre>


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>
set logging on doomseekerdebug.log
(gdb) set logging on doomseekerdebug.log
</pre>
</pre>


GDB has it's own command prompt. Use "run" to start doomseeker.
Use "run" to start doomseeker:
<pre>
<pre>
(gdb) run
(gdb) run
</pre>
</pre>


To start and pass command line parameters to doomseeker.
To start and pass command line parameters to doomseeker:
<pre>
<pre>
(gdb) run <command line parameters>
(gdb) run <command line parameters>
</pre>
</pre>


Use "bt" to get the back trace after a crash.
Use "bt" to get the backtrace after a crash:
<pre>
<pre>
(gdb) bt
(gdb) bt
</pre>
</pre>
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