From: jean-philippe francois <jp.francois@cynove.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PTXdist variables
Date: Fri, 4 Sep 2015 12:31:49 +0200 [thread overview]
Message-ID: <CAGGh5h0m54VT0rxc75tR_KYojF8MpOJ50ww4kqavMG7wqTYTtQ@mail.gmail.com> (raw)
In-Reply-To: <1dfd22ac8c174b4fb5b3630d0258c8d1@GINS-EXC01.gins.local>
2015-08-25 11:01 GMT+02:00 Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>:
> Hi Bruno,
>
> thank you very much for this hint.
>
> But there are much more ptxdist variables (e.a. PTXDIST_TOOLCHAIN or PTXCONF_GNU_TARGET) with are very useful to know in order to write a rule.
> For instance I've to write a rule for a very special kernel module and I need a call like this:
>
It seems that anything that is in selected_ptxconfig or
selected_platformconfig is available, either in rules file, or via
ptxdist print.
and the PTXDIST_* variables are available via
ptxdist bash printenv | grep PTXDIST
Regards,
Jean-Philippe
> make DEVICE=OMAPL1XX \
> SDK=NONE \
> DEPOT==$(PTXDIST_WORKSPACE)/local_src/syslink-2_21_03_11/depot/ \
> LINUXKERNEL=$(PTXDIST_PLATFORMDIR)/build-target/linux-$(PTXCONF_KERNEL_VERSION )/ \
> CGT_ARM_PREFIX=$(PTXDIST_TOOLCHAIN)/$(PTXCONF_GNU_TARGET) \
> IPC_INSTALL_DIR=/opt/ti/ipc_1_25_03_15/ \
> BIOS_INSTALL_DIR=/opt/ti/bios_6_34_04_22/ \
> XDC_INSTALL_DIR=/opt/ti/xdctools_3_24_05_48/ \
> CGT_C674_ELF_INSTALL_DIR=/opt/ti/ti-cgt-c6000_8.0.3/ \
> syslink
>
> It was very hard to find out the ptxdist variables I needed!
>
> Best regards
> Jan-Marc.
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: ptxdist [mailto:ptxdist-bounces@pengutronix.de] Im Auftrag von Bruno Thomsen
> Gesendet: Dienstag, 25. August 2015 08:37
> An: ptxdist@pengutronix.de
> Betreff: Re: [ptxdist] PTXdist variables
>
> Hi Jan-Marc,
>
>> Is there an deterministic way to obtain the list of existent variables for a project?
>
> ptxdist bash printenv
>
> /Bruno
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-09-04 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=CAGGh5h0m54VT0rxc75tR_KYojF8MpOJ50ww4kqavMG7wqTYTtQ@mail.gmail.com \
--to=jp.francois@cynove.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