From: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] PTXdist variables
Date: Tue, 25 Aug 2015 06:24:58 +0000 [thread overview]
Message-ID: <26a4f88ce09e46c995299006d8ab5a6f@GINS-EXC01.gins.local> (raw)
Hi Juergen,
I know this document you have pointed to very well; I've already been working with PTXdist some time.
But looking around existing rules I see, there are a lot useful ptxdist variables and these variables are not described in any documentation I've seen.
For example: there is a variable PROJECT_SPECIFIC_DIR; very useful for a rule that adds files to the root file system.
Other variables are PTXCONF_ARCH_STRING, PTXCONF_KERNEL_CONFIG, PTXCONF_COMPILER_PREFIX, ... and so on.
It is very hard to find out these variables; at the moment I see these only "by accident".
Is there an deterministic way to obtain the list of existent variables for a project?
Best regards,
Jan-Marc.
-----Ursprüngliche Nachricht-----
Von: Juergen Borleis [mailto:jbe@pengutronix.de]
Gesendet: Montag, 24. August 2015 11:16
An: ptxdist@pengutronix.de
Cc: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
Betreff: Re: [ptxdist] PTXdist variables
Hi Jan-Marc,
On Friday 14 August 2015 14:23:46 Stranz Jan-Marc wrote:
> When I'm writing a user defined rule I should use ptxdist variables
> instead absolute paths or values.
>
> There a lot of variables available in a project (e.a.
> PTXDIST_CROSS_CPPFLAGS, PTXDIST_CROSS_LDFLAGS, PTXDIST_PLATFORMCONFIG,
> PTXCONF_GNU_TARGET, ....), but from where do I know the names of these
> variables? How can I obtain a list about available variables for a project?
For example: [1] section 5.1
Regards
Juergen
[1]
http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
--
Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-08-25 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 6:24 Stranz Jan-Marc [this message]
2015-08-25 6:37 ` Bruno Thomsen
2015-08-25 9:01 ` Stranz Jan-Marc
2015-09-04 10:31 ` jean-philippe francois
2015-08-25 7:50 ` Juergen Borleis
-- strict thread matches above, loose matches on Subject: below --
2015-08-14 12:23 Stranz Jan-Marc
2015-08-24 9:15 ` Juergen Borleis
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=26a4f88ce09e46c995299006d8ab5a6f@GINS-EXC01.gins.local \
--to=jm.stranz@gantner-instruments.com \
--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