Re: Conditionally define vars to improve portability

2015-09-08 Thread Jeff King
On Mon, Sep 07, 2015 at 02:51:42PM -0300, Renato Botelho wrote: > Default variables used to build are set using = on Makefile, (e.g. CC, > INSTALL, CFLAGS, …). GNU make overwrite these values if it’s passed as > an argument (make CC=clang) and it works as expected. > > Default method of passing

Re: Conditionally define vars to improve portability

2015-09-08 Thread Renato Botelho
> On Sep 8, 2015, at 03:30, Jeff King wrote: > > On Mon, Sep 07, 2015 at 02:51:42PM -0300, Renato Botelho wrote: > >> Default variables used to build are set using = on Makefile, (e.g. CC, >> INSTALL, CFLAGS, …). GNU make overwrite these values if it’s passed as >> an argument

Re: Conditionally define vars to improve portability

2015-09-08 Thread Junio C Hamano
Jeff King writes: > On Mon, Sep 07, 2015 at 02:51:42PM -0300, Renato Botelho wrote: > >> Default variables used to build are set using = on Makefile, (e.g. CC, >> INSTALL, CFLAGS, …). GNU make overwrite these values if it’s passed as >> an argument (make CC=clang) and it works as

Re: Conditionally define vars to improve portability

2015-09-08 Thread Jacob Keller
On Tue, Sep 8, 2015 at 11:57 AM, Junio C Hamano wrote: > Common things like CC are not so problematic, but more problematic > are various Git build customization in our Makefile that can be left > behind from a previous build. It is easier for users to forget, as > a

Conditionally define vars to improve portability

2015-09-07 Thread Renato Botelho
Default variables used to build are set using = on Makefile, (e.g. CC, INSTALL, CFLAGS, …). GNU make overwrite these values if it’s passed as an argument (make CC=clang) and it works as expected. Default method of passing arguments for make operations on FreeBSD ports tree is using environment