To me, it just makes things less readable.
mcl
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
On 29.07.2011 03:27, Poul-Henning Kamp wrote:
This will make it even harder for people who try to compile our
bits on alien systems without bmake.
Bits referring to multiple directories at once? Using a make flavor, that
already supports .CURDIR, but not .CURDIR:H? Do such things even exist?
P
In message <4e31aed9.4000...@aldan.algebra.com>, "Mikhail T." writes:
>The most common method to refer to the upper directory in Makefile is as
>${.CURDIR}/..
>
>I'd like to propose we begin using ${.CURDIR:H} instead.
This will make it even harder for people who try to compile our
bits on alien
On Thu, Jul 28, 2011 at 11:47 AM, Mikhail T. wrote:
> The most common method to refer to the upper directory in Makefile is as
> ${.CURDIR}/..
>
> I'd like to propose we begin using ${.CURDIR:H} instead. For one this speeds
> up the filesystem-traversal for the invoked tool. And, perhaps more
> im
On 28 July 2011 19:47, Mikhail T. wrote:
> The most common method to refer to the upper directory in Makefile is as
> ${.CURDIR}/..
>
> I'd like to propose we begin using ${.CURDIR:H} instead. For one this speeds
> up the filesystem-traversal for the invoked tool. And, perhaps more
> importantly,
The most common method to refer to the upper directory in Makefile is as
${.CURDIR}/..
I'd like to propose we begin using ${.CURDIR:H} instead. For one this speeds up
the filesystem-traversal for the invoked tool. And, perhaps more importantly, it
makes the various build-logs look nicer (and b
6 matches
Mail list logo
