Lines Matching refs:in
7 All changes mentioned here are more fully described in the GNU make
8 manual, which is contained in this distribution as the file doc/make.texi.
35 variables in scope. This means that in addition to using standard
36 SysV $$@ in prerequisites lists, you can also use complex functions
40 double-quote any "$" in your filenames; instead of "foo: boo$$bar" you
47 In order to comply with POSIX, the way in which GNU make processes
48 backslash-newline sequences in command strings has changed. If your
50 strings in command scripts you will be impacted by this change. See
52 "Splitting Lines"), in section "Command Syntax", chapter "Writing the
53 Commands in Rules", for details.
56 Some previous versions of GNU make had a bug where "#" in a function
59 fixed: if your makefile uses "\#" in a function invocation the
80 call are now masked in the context of the inner call.
84 <thomas.riedl@siemens.com> to track the number of jobs started in the
88 * New special variables available in this release:
91 - .FEATURES: Contains a list of special features available in this
97 in the manual).
98 - New automatic variable: $| (added in 3.80, actually): contains all
101 * New functions available in this release:
102 - $(lastword ...) returns the last word in the list. This gives
127 it will be set in the environment, just as before.
130 in "cmd" or "cmd.exe" (case-insensitive) will force GNU make to use
131 the DOS command interpreter in batch mode even if a UNIX-like shell
148 A complete list of bugs fixed in this version is available here:
156 affect the order in which targets are built, but they do not impact
163 syntax $$@, $$(@D), and $$(@F) in the prerequisites list of a rule.
165 cannot be used in implicit (suffix or pattern) rules. Edouard G. Parmelan
167 decided to implement it in a different way.
172 Similarly, the arguments to "export" (when not used in a variable
181 evaluated as if they had appeared in the makefile. In combination
186 * A new built-in variable is defined, $(MAKEFILE_LIST). It contains a
187 list of each makefile GNU make has read, or started to read, in the
188 order in which they were encountered. So, the last filename in the
192 * A new built-in variable is defined: $(.VARIABLES). When it is
200 * The arguments to $(call ...) functions were being stored in $1, $2,
230 A complete list of bugs fixed in this version is available here:
239 listed in the makefile.
242 superseded in later versions by the .LOW_RESOLUTION_TIME pseudo-target.
271 "normal" targets (not makefiles) that were deemed out of date and in
301 capabilities in a builtin function. Original implementation of this
325 and standard term "prerequisite", both in the manual and in all GNU make
328 * GNU make supports the "big archive" library format introduced in AIX 4.3.
332 support for Solaris and Linux was introduced in 3.77, but the
340 by running "make check" in the distribution. Note that it requires
375 the first or second dependency has an equal sign (=) in its name,
395 * GNU make now uses automake to control Makefile.in generation. This
440 * The directory messages printed by `-w' and implicitly in sub-makes,
444 in the future and gives an error. Files with such impossible timestamps
472 MS-DOS binaries are available for FTP from ftp.simtel.net in
475 * The `MAKEFLAGS' variable (in the environment or in a makefile) can now
480 `MAKEOVERRIDES' variable previously included in the value of `$(MAKE)'
481 for sub-makes is now included in `MAKEFLAGS' instead. As before, you can
482 reset `MAKEOVERRIDES' in your makefile to avoid putting all the variables
483 in the environment when its size is limited.
490 `$^', but preserves duplicates listed in the makefile. This is useful
492 in the link order.
510 * You can now set the variables `binprefix' and/or `manprefix' in
511 Makefile.in (or on the command line when installing) to install GNU make
515 * The built-in Texinfo rules use the new variables `TEXI2DVI_FLAGS' for
525 * It is no longer a fatal error to have a NUL character in a makefile.
526 You should never put a NUL in a makefile because it can have strange
532 C-x ` command takes you there (in case it's a typo you need to fix).
536 * Implicit rule search for archive member references is now done in the
544 Make, and a string describing the remote job support compiled in (if any).
545 Thus the value (in this release) is something like `3.69' or `3.69-Customs'.
547 * Commands in an invocation of the `shell' function are no longer run with
548 a modified environment like target commands are. As in versions before
550 have reversed the change made in version 3.68 because it turned out to
551 cause a paradoxical situation in cases like:
555 When Make attempted to put this variable in the environment for a target
558 for that shell command in the same way, Make would begin to go into an
570 `lib(*.o)' expands to all existing members of `lib' whose names end in
572 of all existing files whose names end in `.a' (e.g. `foo.a(a.o)
585 * Commands in an invocation of the `shell' function are now run with a
597 * Make now supports long-named members in `ar' archive files.
603 to Variables' in the manual for full details.
607 automatically if you use `-C' or `--directory', and in sub-makes; some
610 * The built-in implicit rules now support the alternative extension
624 member references now list only the member name, as in Unix and POSIX.2.
631 commands run simultaneously under -j, as this could result in the two
645 Make runs. Instead, only variables specified on the command line or in
656 to get the old behavior. See the node `Variables/Recursion' in the manual
663 * All fatal error messages now contain `***', so they are easy to find in
668 The library file `libNAME.a' may now be found in the current directory,
671 See the node `Libraries/Search' in the manual for full details.
676 You can also use shell file name patterns in an `include' directive:
682 * You can now use blanks as well as colons to separate the directories in a
685 * You can now use variables and functions in the left hand side of a
686 variable assignment, as in "$(foo)bar = value".
692 * The built-in rules for C++ compilation now use the variables `$(CXX)' and
694 problems with shells that cannot have `+' in environment variable names.
704 * The `-I' switch can now be used in MAKEFLAGS, and are put there
709 * Built-in rules for C++ source files with the `.C' suffix.
715 * Error messages about makefiles are in standard GNU error format,
716 so C-x ` in Emacs works on them.
726 message "Nothing to be done for `phony'" is printed in that case.
736 * The -n, -q, and -t options are not put in the `MAKEFLAGS' and `MFLAG'
740 * If the special target `.NOEXPORT' is specified in a makefile,
751 as well as libLIB.a in /usr/lib, /lib, the current directory, and VPATH.
767 considered out of date and in need of remaking), will not be remade (if they
783 * Library dependencies given as `-lNAME' will use "libNAME.a" in the current
797 * Filenames in rules will now have ~ and ~USER expanded.
805 * The % character can be quoted with backslash in implicit pattern rules,
824 * When the `-w' switch is in effect, and Make has updated makefiles,
832 as it is in Unix make.
836 * The `-j' switch is now put in the MAKEFLAGS and MFLAGS variables when
838 The `-l' switch is not always put in the MAKEFLAGS and MFLAGS variables.
841 The behavior implemented in 3.41 caused too much slowdown.
847 in 3.43 conflicts with RCS.
859 $(FFLAGS). Makefiles designed for System V make may use these variables in
914 * There is support in place for implementations of remote command execution
915 in Make. See the file remote.c.
920 (This number can be changed by redefining MAX_OPEN_DIRECTORIES in dir.c.)
934 * The recursion level indications in error messages are much shorter than
935 they were in version 3.14.
946 * Variables that are defaults built into Make will not be put in the
952 * Hopefully some speed-up for large directories due to a change in the
957 * Default makefiles that don't exist will be remade and read in.
1002 GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY