From f99eea8f90ce4b75aa9409a541f10fed3d4e1f55 Mon Sep 17 00:00:00 2001 From: floam Date: Fri, 4 Nov 2005 03:17:45 +0000 Subject: * Instructions page near-done git-svn-id: svn://svn.icculus.org/quake3/trunk@255 edf5b092-35ff-0310-97b2-ce42778d08ea --- web/include/instruc.php | 54 +++++++++++++++++++++++++++++++++++++------------ 1 file changed, 41 insertions(+), 13 deletions(-) (limited to 'web/include/instruc.php') diff --git a/web/include/instruc.php b/web/include/instruc.php index 68361db..409009d 100644 --- a/web/include/instruc.php +++ b/web/include/instruc.php @@ -1,4 +1,6 @@

Check out and build from Subversion

+

(This part assumes Windows users are using Cygwin. If you aren't, +TortoiseSVN is a good client.)

  1. Change into a directory that you want the tree to be kept in.
  2. Check out the source tree:
    @@ -8,29 +10,55 @@ svn co svn://svn.icculus.org/quake3/trunk quake3 -r100)
  3. Read the readme file. Really. Do it.
    4. -
  4. Compile and install Quake III. +
  5. Compile and install Quake 3:

    • Linux and friends

        +
      1. Install Quake 3 for Linux using the latest point release + installer. While the Quake3 engine is Free Software, you + still need to copy over legal PK3s like before.
      2. Change into the top level directory (it contains the ui and code directories.)
        3. -
      3. Run make
        4. -
      4. Create a directory to install Quake3 into:
        - mkdir /usr/local/games/quake3
        5. -
      5. Copy - +
      6. Run make.
        7. +
      7. Set $COPYDIR to the directory + you installed Quake3 to and make the copyfiles target. + Make sure you are changed to the owner of this path (probably + root).
        + COPYDIR="/opt/quake3" make copyfiles

    • Windows

      -
        -
      1. -
      +

      Building on Windows is slightly complicated. You can either + use Microsoft Visual C++ or MinGW. MinGW works better currently; + both methods are described in the + readme + you already are supposed to have read.

    6. +
  6. If everything has gone well, you should have a binary that works! If not, seek help.
-

How to submit your changes:

-

rules rules rules, angry zakk-style text rules rules rules, angry zakk-style text rules rules rules, angry zakk-style text rules rules rules, angry zakk-style text rules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style text

-

rules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style text

-

rules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style textrules rules rules, angry zakk-style text rules rules rules, angry zakk-style textrules rules rules, angry zakk-style text

+

Pay your dues, contribute!

+

If you've come up with an improvement or fixed something, we'd love to hear about it! +Firstly, try to make sure that the patch breaks less than it fixes. We don't +require everyone to be decorated Geniuses, but do attempt to produce a patch that you've +tested and at list sort-of understand what you're doing.

+

Not everyone who knows C knows how to use diff (the tool +you need to create patches with), and not everyone is making patches against the C code. +That's okay, here's the 10ยข survival guide to making patches:

+ +

For more information on diff and patch, +read their man-pages.

+

The prefered way to get the ball rolling on a patch is to file a bug +for your patch and attach the patch to it and then send a notice to the mailing list +about it. If you're really so lazy that you can't do this, we would prefer you at least +mail it to zakk@icculus.org rather than not do +anything.

-- cgit v1.2.3