mirror of
https://github.com/gnustep/tools-make.git
synced 2025-04-22 22:00:49 +00:00
Added long comment explaining the difference between AUXILIARY_XXX and
ADDITIONAL_XXX git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@12214 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
parent
2c2b9d72e0
commit
7c7c420fbe
2 changed files with 41 additions and 0 deletions
|
@ -1,3 +1,8 @@
|
|||
Fri Jan 25 12:08:30 2002 Nicola Pero <nicola@brainstorm.co.uk>
|
||||
|
||||
* rules.make: Added long comment explaining the difference between
|
||||
ADDITIONAL_XXX and AUXILIARY_XXX.
|
||||
|
||||
2002-01-25 Richard Frith-Macdonald <rfm@gnu.org>
|
||||
|
||||
* GNUstep.sh.in: Add some quoting to make paths to user GNUstep.sh
|
||||
|
|
36
rules.make
36
rules.make
|
@ -299,6 +299,42 @@ ifeq ($(AUTO_DEPENDENCIES_FLAGS),)
|
|||
endif
|
||||
endif
|
||||
|
||||
# The difference between ADDITIONAL_XXXFLAGS and AUXILIARY_XXXFLAGS is the
|
||||
# following:
|
||||
#
|
||||
# ADDITIONAL_XXXFLAGS are set freely by the user GNUmakefile
|
||||
#
|
||||
# AUXILIARY_XXXFLAGS are set freely by makefile fragments installed by
|
||||
# auxiliary packages. For example, gnustep-db installs
|
||||
# a gdl.make file. If you want to use gnustep-db in
|
||||
# your tool, you `include $(GNUSTEP_MAKEFILES)/gdl.make'
|
||||
# and that will add the appropriate flags to link against
|
||||
# gnustep-db. Those flags are added to AUXILIARY_XXXFLAGS.
|
||||
#
|
||||
# Why can't ADDITIONAL_XXXFLAGS and AUXILIARY_XXXFLAGS be the same variable ?
|
||||
# Good question :-) I'm not sure but I think the original reason is that
|
||||
# users tend to think they can do whatever they want with ADDITIONAL_XXXFLAGS,
|
||||
# like writing
|
||||
# ADDITIONAL_XXXFLAGS = -Verbose
|
||||
# (with a '=' instead of a '+=', thus discarding the previous value of
|
||||
# ADDITIONAL_XXXFLAGS) without caring for the fact that other makefiles
|
||||
# might need to add something to ADDITIONAL_XXXFLAGS.
|
||||
#
|
||||
# So the idea is that ADDITIONAL_XXXFLAGS is reserved for the users to
|
||||
# do whatever mess they like with them, while in makefile fragments
|
||||
# from packages we use a different variable, which is subject to a stricter
|
||||
# control, requiring package authors to always write
|
||||
#
|
||||
# AUXILIARY_XXXFLAGS += -Verbose
|
||||
#
|
||||
# in their auxiliary makefile fragments, to make sure they don't
|
||||
# override flags from different packages, just add to them.
|
||||
#
|
||||
# When building up command lines inside gnustep-make, we always need
|
||||
# to add both AUXILIARY_XXXFLAGS and ADDITIONAL_XXXFLAGS to all
|
||||
# compilation/linking/etc command.
|
||||
#
|
||||
|
||||
ALL_CPPFLAGS = $(AUTO_DEPENDENCIES_FLAGS) $(CPPFLAGS) $(ADDITIONAL_CPPFLAGS) \
|
||||
$(AUXILIARY_CPPFLAGS)
|
||||
|
||||
|
|
Loading…
Reference in a new issue