quakeforge/cs-code/menu.src.in

menu.dat

@srcdir@/cbuf_def.qc
@srcdir@/draw_def.qc
@srcdir@/file_def.qc
@srcdir@/inputline_def.qc
@srcdir@/menu_def.qc
@srcdir@/string_def.qc

@srcdir@/menu.qc
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			`menu.dat`

more work on the mp menus and split out most of the builtin defs 2002-01-23 19:41:50 +00:00			`@srcdir@/cbuf_def.qc`
			`@srcdir@/draw_def.qc`
			`@srcdir@/file_def.qc`
start implementing the api for input lines and clean up a couple csqc prototype issues. 2002-01-23 22:37:44 +00:00			`@srcdir@/inputline_def.qc`
more work on the mp menus and split out most of the builtin defs 2002-01-23 19:41:50 +00:00			`@srcdir@/menu_def.qc`
			`@srcdir@/string_def.qc`

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			`@srcdir@/menu.qc`