mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Richard Günther" <richard.guenther@garz-fricke.com>
To: "Jürgen Beisert" <jbe@pengutronix.de>
Subject: Re: [ptxdist] Problem with variable reference in Makefiles
Date: Thu, 31 Oct 2013 10:21:55 +0100	[thread overview]
Message-ID: <D99582E5322435468A77E74BB0039E7B3E5B7123FC@SRV02.hamburg.garz-fricke.de> (raw)

Dear Juergen,

> The tool 'make' includes all rule files in a specific order. And I guess also the locale has some effect on this order. But PTXdist ensures the local > is set to 'C'.
> 
> Did you only try with different _variable_ names or with different _rule_file_ names as well?

I tried with different rule-file names in the project-specific rules directory as well. I used the following lines for testing:

TEST1 := $(AUTOMADDEL_VERSION)	(automaddel.make  is in the project-specific rules directory)
TEST2 := $(AUTOMODDEL_VERSION)	(automoddel.make   is in the project-specific rules directory)
TEST3 := $(XORG_SERVER_VERSION)	(xorg-server.make  is in the ptxdist default rules directory)

I put the three lines into Makefiles in my project-specific rules directory and got the following results:
- busybox.make: all variables TEST1, TEST2 and TEST3 are empty.
-  shiboken.make: TEST1 contains the correct value, TEST2 is empty, and TEST3 contains the correct value.
- xconfig.make: all variables TEST1, TEST2 and TEST3 are empty 

Regards,
Richard  
-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-10-31 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  9:21 Richard Günther [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31  7:35 Richard Günther
2013-10-31  8:07 ` Jürgen Beisert
2013-10-29 14:37 Richard Günther
2013-10-29 14:49 ` Andreas Bießmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D99582E5322435468A77E74BB0039E7B3E5B7123FC@SRV02.hamburg.garz-fricke.de \
    --to=richard.guenther@garz-fricke.com \
    --cc=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox