From: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] PTXdist variables
Date: Fri, 14 Aug 2015 12:23:46 +0000 [thread overview]
Message-ID: <2c230f09709240e3bc4499c195b826f0@GINS-EXC01.gins.local> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 418 bytes --]
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?
Best regards,
Jan-Marc Stranz.
[-- Attachment #1.2: Type: text/html, Size: 2666 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-08-14 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 12:23 Stranz Jan-Marc [this message]
2015-08-24 9:15 ` Juergen Borleis
2015-08-25 6:24 Stranz Jan-Marc
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
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=2c230f09709240e3bc4499c195b826f0@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