Re: [Cryptodev-linux-devel] [PATCH] allow user override for kernel and installation directory

2013-06-28 Thread Stoica Cristian-B18196
 This patch shouldn't be necessary: you can give variable assignments
 as arguments on the command line, and they should override basic
 assignment within the makefile.
[] 
Thanks - I was not aware of that. I always exported the variables before 
calling make. You learn something new every day.

Cristian S.
___
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel


Re: [Cryptodev-linux-devel] [PATCH] allow user override for kernel and installation directory

2013-06-27 Thread Phil Sutter
Hi,

On Thu, Jun 27, 2013 at 05:39:59PM -0600, Anthony Foiani wrote:
 Cristian --
 
 On Thu, Jun 27, 2013 at 7:42 AM, Cristian Stoica
 cristian.sto...@freescale.com wrote:
  - this is useful for cross-building for embedded systems
 
 This patch shouldn't be necessary: you can give variable assignments
 as arguments on the command line, and they should override basic
 assignment within the makefile.  See:

But it still makes sense, since overriding them is possible only when
passing the variable assignment as parameter to make, not via
environment variable.

Take this sample Makefile:
| foo1 = bar
| foo2 ?= bar
| 
| all:
|   @echo ${foo1} ${foo2}


Then look at the changing output:
| $ make foo1=foo foo2=foo
| foo foo
| $ foo1=foo foo2=foo make
| bar foo

Although it may be possible to overwrite the variables when calling
make, there certainly are build systems passing make variables via
environment.

Greetings, Phil

___
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel