quakeforge/cs-code
Bill Currie 8a24b28d97 scary, but the only changes qfcc needed to build as part of quakeforge was
to auto-substitued the libs and headers.

 o  unconditionally build qfcc (for now, anyway) when building quakeforge
    (needed for cs-code compilation)
 o  when built as part of quakeforge (qfcc should still be buildable
    independently) always enable cpp
 o  autoconfiscate the client-side code
 o  build the client-side code using the built qfcc
 o  install the client-side code in $(datadir)/quakeforge/id1
2002-01-22 05:48:03 +00:00
..
.gitignore scary, but the only changes qfcc needed to build as part of quakeforge was 2002-01-22 05:48:03 +00:00
console.qc throw this in cvs for now. it's not used at all, and I don't know if I plan 2002-01-21 21:46:57 +00:00
Makefile.am scary, but the only changes qfcc needed to build as part of quakeforge was 2002-01-22 05:48:03 +00:00
menu.qc start on the multiplayer menu 2002-01-21 21:39:27 +00:00
menu.src.in scary, but the only changes qfcc needed to build as part of quakeforge was 2002-01-22 05:48:03 +00:00