From 1fa110cf268a6d3712ca57e77177caec6756772a Mon Sep 17 00:00:00 2001 From: floam Date: Sat, 5 Nov 2005 01:03:32 +0000 Subject: Rename instructions page and mention SDL for Windows git-svn-id: svn://svn.icculus.org/quake3/trunk@276 edf5b092-35ff-0310-97b2-ce42778d08ea --- web/include/instruc.php | 95 ------------------------------------------------- 1 file changed, 95 deletions(-) delete mode 100644 web/include/instruc.php (limited to 'web/include/instruc.php') diff --git a/web/include/instruc.php b/web/include/instruc.php deleted file mode 100644 index fc119ea..0000000 --- a/web/include/instruc.php +++ /dev/null @@ -1,95 +0,0 @@ -

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. -
  2. Check out the source tree:
    - svn co svn://svn.icculus.org/quake3/trunk quake3 -
    - (You can check out a specific revision with the -r option, like this: - svn co svn://svn.icculus.org/quake3/trunk quake3 -r100) -
    3. -
  3. Read the readme - file. Really. Do it.
    4. -
  4. 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. -
      2. Change into the top level directory (it contains the - ui and code - directories.)
        3. -
      3. Run make.
        4. -
      4. 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
        5. -
      -
      • -

    • Windows

      -

      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.

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

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.

- -

The preferred way to get the ball rolling on a patch is to file a -Bugzilla bug for your request with the patch attached -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 at all.

- -

Please make it clear if the patch you're submitting for inclusion isn't yours, and point out where you found it and who authored it. This is so we know who to attribute blame to when it horribly -breaks things credit to.

- -

Generating Patches

-

If you know how to code, but never made a patch before, that's okay. Here's the 10ยข -survival guide to generating patches.

- -

For more information on diff, patch, -and svn, read their respective man -and info pages. For a more in-depth guide on Subversion take -a look at the SVN -Book.

-- cgit v1.2.3