I've grossly simplified the above example to show the gist of it, but the
intermediate steps
are all first-order targets for debugging and development purposes. I
started using macros
but the amount of nesting and $-escaping needed makes that approach fragile
and hard for
non-expert users to manage
On Fri, Aug 9, 2013 at 12:59 PM, Ed Hutchins wrote:
...
> In my case I'd like to have "init", "start" and "start_clean" end-user
> targets which reuse common
> targets which in turn depend on targets specified by the above semantic
> intent. If there were a
> true order-only operator (say ||), I c
The following Makefile:
condset: COND ?= one
condset: condset2
@echo $@ COND [$(COND)]
condset2: COND ?= two
condset2: condset3
@echo $@ COND [$(COND)]
condset3: COND ?= three
condset3:
@echo $@ COND [$(COND)]
outputs:
condset3 COND [three]
condset2 COND [two]
condset COND [one]
I would have
Hello!
This patch fixes up Windows build using .bat files. The two issues are:
1. New compilers have inttypes.h file, current config.h.W32 causes compile
errors because of uintmax_t redefinition (it ends up in attempt to use
something like long long long).
2. Test suite now passes TEMP and TMP
Hello! This is the new patch. Allows to enable DOS paths on Cygwin with no
abspath breaking.
The idea of the change: instead of single HAVE_DOS_PATHS definition we now
have two definitions:
1. HAVE_DOS_PATHS - says that the platform is capable of handling DOS paths
in principle.
2. NATIVE_DOS_PA
