qf/quakeforge
0
0
Fork 0
mirror of https://git.code.sf.net/p/quake/quakeforge synced 2024-11-11 15:51:36 +00:00
Code Issues Projects Releases Packages Wiki Activity
quakeforge/cs-code/Makefile.am

21 lines
686 B
Text
Raw Normal View History

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
wonder how I forgot the -Werror...
2002-03-14 18:51:25 +00:00
QCFLAGS=-g -Werror
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
QCPPFLAGS=-I. -I$(srcdir) -I$(top_builddir)/include -I$(top_srcdir)/include
pkgdata_DATA= menu.dat
the early beginnings of the serverlist qc
2002-02-17 00:21:48 +00:00
menu_src= menu.qc servlist.qc options.qc cbuf_def.qc cvar_def.qc draw_def.qc file_def.qc game_def.qc inputline_def.qc key_defs.qc menu_def.qc options_util.qc string_def.qc controls_o.qc
more make dist fixes
2002-01-22 18:04:03 +00:00
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
Reference in a new issue Copy permalink