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

cs-code/.gitignore

@@ -1,4 +1,6 @@
 *.dat
 *.h
+*.src
 *.sym
 .vimrc
+Makefile.in

cs-code/Makefile

@@ -1,7 +0,0 @@
-all: menu.dat
-
-menu.dat: menu.src menu.qc
-	qfcc -g -I../include -P menu.src
-
-clean:
-	rm -f core *.dat *.h *.sym

cs-code/Makefile.am

@@ -0,0 +1,18 @@
+## Process this file with automake to produce Makefile.in
+AUTOMAKE_OPTIONS= foreign
+
+#FIXME should qf data be installed somewhere other than id1 that gets
+#searched after everything else?
+pkgdatadir=$(datadir)/quakeforge/id1
+
+QFCC=$(top_builddir)/tools/qfcc/source/qfcc
+QCFLAGS=-g
+QCPPFLAGS=-I. -I$(srcdir) -I$(top_builddir)/include -I$(top_srcdir)/include
+
+pkgdata_DATA= menu.dat
+
+menu.dat: menu.src menu.qc
+	$(QFCC) $(QCFLAGS) $(QCPPFLAGS) -P $<
+
+EXTRA_DIST=	
+CLEANFILES= *.dat *.sym

cs-code/menu.src

@@ -1,3 +0,0 @@
-menu.dat
-
-menu.qc

cs-code/menu.src.in

@@ -0,0 +1,3 @@
+menu.dat
+
+@srcdir@/menu.qc