[ptxdist] PTXdist variables

[ptxdist] PTXdist variables

[Stranz Jan-Marc]

[-- 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

Re: [ptxdist] PTXdist variables

[Juergen Borleis]

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

Re: [ptxdist] PTXdist variables

[jean-philippe francois]

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

[ptxdist] PTXdist variables

[Stranz Jan-Marc]

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: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

Re: [ptxdist] PTXdist variables

[Juergen Borleis]

Hi Jan-Marc,

On Tuesday 25 August 2015 08:24:58 Stranz Jan-Marc wrote:
> 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.

Base problem is, those developers who add these variables are not those 
developers who write the documentation.... I'm always behind when writing 
documentation.

If you have some text snippets for those yet undocumented variables I will 
happily add them to the ptxdist guru guide :)

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] PTXdist variables

[Bruno Thomsen]

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] PTXdist variables

[Stranz Jan-Marc]

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