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'
21 # of any given module. I notice that the very latest gmake has the concept
22 # of local variables for rules. It is possible this feature in conjunction
23 # with the generated names will provide a very powerfull solution indeed!
25 # A build directory is used by default, all generated items get put into
26 # there. However unlike automake this is not done with a VPATH build
27 # (vpath builds break the distinction between #include "" and #include <>)
28 # but by explicly setting the BUILD variable. Make is invoked from
29 # within the source itself which is much more compatible with compilation
35 # Search for the build directory
37 BUILD_POSSIBLE := $(BUILD) $(BASE)/$(BUILD)
39 BUILD_POSSIBLE := $(BASE) $(BASE)/build
42 BUILDX:= $(foreach i,$(BUILD_POSSIBLE),$(wildcard $(i)/environment.mak*))
43 BUILDX:= $(patsubst %/,%,$(firstword $(dir $(BUILDX))))
45 ifeq ($(words $(BUILDX)),0)
47 echo Can't find the build directory in $(BUILD_POSSIBLE) -- use BUILD=
50 override BUILD := $(BUILDX)
53 INCLUDE := $(BUILD)/include
56 OBJ := $(BUILD)/obj/$(SUBDIR)
61 LIBRARY_H = $(BASE)/buildlib/library.mak
62 DEBIANDOC_H = $(BASE)/buildlib/debiandoc.mak
63 MANPAGE_H = $(BASE)/buildlib/manpage.mak
64 PROGRAM_H = $(BASE)/buildlib/program.mak
66 # Source location control
67 # SUBDIRS specifies sub components of the module that
68 # may be located in subdrictories of the source dir.
69 # This should be declared before including this file
72 # Header file control.
73 # TARGETDIRS indicitates all of the locations that public headers
74 # will be published to.
75 # This should be declared before including this file
79 include $(BUILD)/environment.mak
80 CPPFLAGS+= -I$(INCLUDE)
83 # Phony rules. Other things hook these by appending to the dependency
85 .PHONY: headers library clean veryclean all binary program doc
86 .PHONY: maintainer-clean dist-clean distclean pristine sanity
88 binary: library program
89 maintainer-clean dist-clean distclean pristine sanity: veryclean
90 headers library clean veryclean program:
92 # Header file control. We want all published interface headers to go
93 # into the build directory from thier source dirs. We setup some
96 $(INCLUDE)/%.h $(addprefix $(INCLUDE)/,$(addsuffix /%.h,$(HEADER_TARGETDIRS))) : %.h
99 # Dependency generation. We want to generate a .d file using gnu cpp.
100 # For GNU systems the compiler can spit out a .d file while it is compiling,
101 # this is specified with the INLINEDEPFLAG. Other systems might have a
102 # makedep program that can be called after compiling, that's illistrated
103 # by the DEPFLAG case.
104 # Compile rules are expected to call this macro after calling the compiler
107 sed -e "1s/.*:/$(subst /,\\/,$@):/" $(basename $(@F)).d > $(DEP)/$(basename $(@F)).d
108 -rm -f $(basename $(@F)).d
113 $(CXX) $(DEPFLAG) $(CPPFLAGS) -o $@ $<
114 sed -e "1s/.*:/$(subst /,\\/,$@):/" $(basename $(@F)).d > $(DEP)/$(basename $(@F)).d
115 -rm -f $(basename $(@F)).d