quakeforge/cs-code/Makefile.am

## 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=@sharepath@/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_src= menu.qc

menu.dat: menu.src $(menu_src)
	$(QFCC) $(QCFLAGS) $(QCPPFLAGS) -P $<

EXTRA_DIST= $(menu_src)
CLEANFILES= *.dat *.sym
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			`## 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?`
d'oh, should be installing into fs_sharepath :P 2002-01-22 06:22:52 +00:00			`pkgdatadir=@sharepath@/id1`
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
			`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`

more make dist fixes 2002-01-22 18:04:03 +00:00			`menu_src= menu.qc`

			`menu.dat: menu.src $(menu_src)`
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			`$(QFCC) $(QCFLAGS) $(QCPPFLAGS) -P $<`

more make dist fixes 2002-01-22 18:04:03 +00:00			`EXTRA_DIST= $(menu_src)`
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			`CLEANFILES= .dat .sym`