warzone2100/makerules/lib.mk

include $(top_srcdir)/makerules/common.mk

.PHONY: all clean

all: $(top_builddir)/lib/lib$(LIB).a

$(top_builddir)/lib/lib$(LIB).a: $(patsubst %.c,%.o,$(patsubst %.cpp,%.o,$(SRC)))
	$(AR) rcv $(subst /,\\,$@) $^

clean:
	$(RM_F) $(subst /,\\,$(top_builddir)/lib/lib$(LIB).a) *.o $(CLEANFILES)
Use the (also new in this commit) relative variants of the directories almost everywhere. Exception is when generating the .wz files, where we need the path to the build directory and building a reverse relative path to $(srcdir) will be messy. Also silence submake.mk a great deal. Bug #11883 should be fixed now for the most part. git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5325 4a71c877-e1ca-e34f-864e-861f7616d084 2008-06-24 16:41:52 -07:00			`include $(top_srcdir)/makerules/common.mk`
Create final repository structure. git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@362 4a71c877-e1ca-e34f-864e-861f7616d084 2007-06-28 10:47:08 -07:00
Boost raw Makefiles - Use PACKAGE, PACKAGE_VERSION, remove VERSION - Allow out-of-source-dir builds (mkdir build && cd build && make -f ../Makefile.raw) - Move config.mk from $(top_srcdir)/makerules/config.mk to $(top_builddir)/config.mk When keeping current behaviour (srcdir=builddir), this means: Move it from makerules into the main directory git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5308 4a71c877-e1ca-e34f-864e-861f7616d084 2008-06-23 06:54:47 -07:00			`.PHONY: all clean`

Use the (also new in this commit) relative variants of the directories almost everywhere. Exception is when generating the .wz files, where we need the path to the build directory and building a reverse relative path to $(srcdir) will be messy. Also silence submake.mk a great deal. Bug #11883 should be fixed now for the most part. git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5325 4a71c877-e1ca-e34f-864e-861f7616d084 2008-06-24 16:41:52 -07:00			`all: $(top_builddir)/lib/lib$(LIB).a`
Lets use some proper make rules! * Use $@ and $< to refer to the targets and dependencies of make rules * Don't refer to make rule dependencies and targets by copying them! * Putting make rules on multiple lines isn't bad, in fact it increases readability! * Mark phony make rules (i.e. rules who's actions don't produce files) as `.PHONY` git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@4846 4a71c877-e1ca-e34f-864e-861f7616d084 2008-04-28 13:58:13 -07:00
Use the (also new in this commit) relative variants of the directories almost everywhere. Exception is when generating the .wz files, where we need the path to the build directory and building a reverse relative path to $(srcdir) will be messy. Also silence submake.mk a great deal. Bug #11883 should be fixed now for the most part. git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5325 4a71c877-e1ca-e34f-864e-861f7616d084 2008-06-24 16:41:52 -07:00			`$(top_builddir)/lib/lib$(LIB).a: $(patsubst %.c,%.o,$(patsubst %.cpp,%.o,$(SRC)))`
Reduce "raw" Makefiles to "win32" Makefiles by removing logic from configure.mk Command variables stay, but DIRSEP variable got removed git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5401 4a71c877-e1ca-e34f-864e-861f7616d084 2008-07-06 07:28:50 -07:00			`$(AR) rcv $(subst /,\\,$@) $^`
Lets use some proper make rules! * Use $@ and $< to refer to the targets and dependencies of make rules * Don't refer to make rule dependencies and targets by copying them! * Putting make rules on multiple lines isn't bad, in fact it increases readability! * Mark phony make rules (i.e. rules who's actions don't produce files) as `.PHONY` git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@4846 4a71c877-e1ca-e34f-864e-861f7616d084 2008-04-28 13:58:13 -07:00
			`clean:`
Reduce "raw" Makefiles to "win32" Makefiles by removing logic from configure.mk Command variables stay, but DIRSEP variable got removed git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@5401 4a71c877-e1ca-e34f-864e-861f7616d084 2008-07-06 07:28:50 -07:00			`$(RM_F) $(subst /,\\,$(top_builddir)/lib/lib$(LIB).a) *.o $(CLEANFILES)`