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:
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:[email protected]] Im Auftrag von Bruno
Thomsen
Gesendet: Dienstag, 25. August 2015 08:37
An: [email protected]
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
[email protected]
--
ptxdist mailing list
[email protected]
