List Info

Thread: is it problematic to "call" a non-existent define?




is it problematic to "call" a non-existent define?
user name
2007-12-21 15:54:52
  is there any problem with invoking $(call fred) if
"fred" hasn't
been defined?  that is, is "call" defined to just
quietly pass over
that and keep going?  thanks.

rday

============================================================
============
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
============================================================
============


_______________________________________________
Help-make mailing list
Help-makegnu.org
http:
//lists.gnu.org/mailman/listinfo/help-make

RE: is it problematic to "call" a non-existent define?
country flaguser name
United Kingdom
2007-12-22 04:37:16
On 21 December 2007 21:55, Robert P. J. Day wrote:

>   is there any problem with invoking $(call fred) if
"fred" hasn't
> been defined?  that is, is "call" defined to
just quietly pass over
> that and keep going?  thanks.

  No problem at all, and yes, if you call an undefined
variable, it expands to
nothing - which of course is then unchanged by applying the
arguments since it
doesn't contain any $(1) etc.  You'll get a warning message
if you've used
"--warn-undefined-variables" on the command line.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....



_______________________________________________
Help-make mailing list
Help-makegnu.org
http:
//lists.gnu.org/mailman/listinfo/help-make

RE: is it problematic to "call" a non-existent define?
user name
2007-12-22 05:32:23
On Sat, 22 Dec 2007, Dave Korn wrote:

> On 21 December 2007 21:55, Robert P. J. Day wrote:
>
> >   is there any problem with invoking $(call fred)
if "fred" hasn't
> > been defined?  that is, is "call"
defined to just quietly pass over
> > that and keep going?  thanks.
>
>   No problem at all, and yes, if you call an undefined
variable, it expands to
> nothing - which of course is then unchanged by applying
the arguments since it
> doesn't contain any $(1) etc.  You'll get a warning
message if you've used
> "--warn-undefined-variables" on the command
line.
>
>     cheers,
>       DaveK

i suspected as much, i was just curious if it was a standard
make
technique to do that sort of thing.  thanks.

rday
--

============================================================
============
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
============================================================
============


_______________________________________________
Help-make mailing list
Help-makegnu.org
http:
//lists.gnu.org/mailman/listinfo/help-make

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )