3 # This file configures the default environment for the make system
4 # The way it works is fairly simple, each module is defined in it's
5 # own *.mak file. It expects a set of variables to be set to values
6 # for it to operate as expected. When included the module generates
7 # the requested rules based on the contents of its control variables.
9 # This works out very well and allows a good degree of flexability.
10 # To accomidate some of the features we introduce the concept of
11 # local variables. To do this we use the 'Computed Names' feature of
12 # gmake. Each module declares a LOCAL scope and access it with,
14 # This works very well but it is important to rembember that within
15 # a rule the LOCAL var is unavailble, it will have to be constructed
16 # from the information in the rule invokation. For stock rules like
17 # clean this is simple, we use a local clean rule called clean/$(LOCAL)
18 # and then within the rule $(@F) gets back $(LOCAL)! Other rules will
19 # have to use some other mechanism (filter perhaps?) The reason such
20 # lengths are used is so that each directory can contain several 'instances'
23 # A build directory is used by default, all generated items get put into
24 # there. However unlike automake this is not done with a VPATH build
25 # (vpath builds break the distinction between #include "" and #include <>)
26 # but by explicly setting the BUILD variable. Make is invoked from
27 # within the source itself which is much more compatible with compilation
33 # Search for the build directory
35 BUILD_POSSIBLE := $(BUILD) $(BASE)/$(BUILD)
37 BUILD_POSSIBLE := $(BASE) $(BASE)/build
40 BUILDX:= $(foreach i,$(BUILD_POSSIBLE),$(wildcard $(i)/environment.mak*))
41 BUILDX:= $(patsubst %/,%,$(firstword $(dir $(BUILDX))))
43 ifeq ($(words $(BUILDX)),0)
45 echo Can't find the build directory in $(BUILD_POSSIBLE) -- use BUILD=
48 override BUILD := $(BUILDX)
51 INCLUDE := $(BUILD)/include
54 OBJ := $(BUILD)/obj/$(SUBDIR)
59 LIBRARY_H = $(BASE)/buildlib/library.mak
60 DEBIANDOC_H = $(BASE)/buildlib/debiandoc.mak
61 MANPAGE_H = $(BASE)/buildlib/manpage.mak
62 PROGRAM_H = $(BASE)/buildlib/program.mak
64 # Source location control
65 # SUBDIRS specifies sub components of the module that
66 # may be located in subdrictories of the source dir.
67 # This should be declared before including this file
70 # Header file control.
71 # TARGETDIRS indicitates all of the locations that public headers
72 # will be published to.
73 # This should be declared before including this file
77 include $(BUILD)/environment.mak
78 CPPFLAGS+= -I$(INCLUDE)
81 # Phony rules. Other things hook these by appending to the dependency
83 .PHONY: headers library clean veryclean all binary program doc
84 .PHONY: maintainer-clean dist-clean distclean pristine sanity
86 binary: library program
87 maintainer-clean dist-clean distclean pristine sanity: veryclean
88 headers library clean veryclean program:
90 # Header file control. We want all published interface headers to go
91 # into the build directory from thier source dirs. We setup some
94 $(INCLUDE)/%.h $(addprefix $(INCLUDE)/,$(addsuffix /%.h,$(HEADER_TARGETDIRS))) : %.h
97 # Dependency generation. We want to generate a .d file using gnu cpp.
98 # For GNU systems the compiler can spit out a .d file while it is compiling,
99 # this is specified with the INLINEDEPFLAG. Other systems might have a
100 # makedep program that can be called after compiling, that's illistrated
101 # by the DEPFLAG case.
102 # Compile rules are expected to call this macro after calling the compiler
105 sed -e "1s/.*:/$(subst /,\\/,$@):/" $(basename $(@F)).d > $(DEP)/$(basename $(@F)).d
106 -rm -f $(basename $(@F)).d
111 $(CXX) $(DEPFLAG) $(CPPFLAGS) -o $@ $<
112 sed -e "1s/.*:/$(subst /,\\/,$@):/" $(basename $(@F)).d > $(DEP)/$(basename $(@F)).d
113 -rm -f $(basename $(@F)).d