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:j...@pengutronix.de] Gesendet: Montag, 24. August 2015 11:16 An: ptxdist@pengutronix.de Cc: Stranz Jan-Marc <jm.str...@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
