Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!

Difference between revisions of "Idontknowthisguy:Hacking Quake"

From Quake Wiki

(Creation of the page; includes intro and DarkPlaces makefile info)
 
(further down the rabbit hole)
 
Line 8: Line 8:
  
 
==Darkplaces Hacking==
 
==Darkplaces Hacking==
 +
===Makefile===
 
To get started, look at the makefile. The makefile is how you compile the program, so it should give us some pretty good hints on where to start looking. What it does:
 
To get started, look at the makefile. The makefile is how you compile the program, so it should give us some pretty good hints on where to start looking. What it does:
 
# determine the platform (Windows, BSD, OS X, Solaris, or Linux)  
 
# determine the platform (Windows, BSD, OS X, Solaris, or Linux)  
Line 15: Line 16:
 
# includes makefile.inc, which has variable definitions shared by all makefiles
 
# includes makefile.inc, which has variable definitions shared by all makefiles
 
I don't know what the rest does, but I hazard a guess that it's not all that important.
 
I don't know what the rest does, but I hazard a guess that it's not all that important.
 +
===make Output===
 +
It compiles the source according to the platform specifications and options selected, then compiles the files in alphabetical order. Let's take a look at them.
 +
===cl_===
 +
====collision====

Latest revision as of 11:24, 5 June 2009

I've looked around and found no real documentation on Quake hacking. I'm sure I'll find some eventually, but I want to document my experience, and hopefully help some people who will be in the position I'm in now. This wiki is a solid resource, so hopefully my additions will be a useful contribution.

I'll begin with the DarkPlaces engine by Lord Havoc, but hopefully move on to others, like the Twilight engine; maybe making specific docs for each, but hopefully having an engine agnostic reference to tie it all together.

Good References[edit]

Darkplaces Hacking[edit]

Makefile[edit]

To get started, look at the makefile. The makefile is how you compile the program, so it should give us some pretty good hints on where to start looking. What it does:

  1. determine the platform (Windows, BSD, OS X, Solaris, or Linux)
  2. gathers info based on the platform (architecture)
  3. sets the variables to be used in compilation for the appropriate platform
  4. sets the sound variables based on what you passed to make or the platform
  5. includes makefile.inc, which has variable definitions shared by all makefiles

I don't know what the rest does, but I hazard a guess that it's not all that important.

make Output[edit]

It compiles the source according to the platform specifications and options selected, then compiles the files in alphabetical order. Let's take a look at them.

cl_[edit]

collision[edit]