mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Extract a list of all packages
Date: Thu, 30 Jan 2014 20:31:59 +0100	[thread overview]
Message-ID: <20140130193159.GB3223@pengutronix.de> (raw)
In-Reply-To: <6B919AC79333344DB0660E3FADEB2165052E8CB1B0AB@BYTECEXCHGSRV.bytecexchg.local>

Hi,

On Thu, Jan 30, 2014 at 02:58:11PM +0100, Bernhard Bender wrote:
> Von: Juergen Beisert [mailto:jbe@pengutronix.de]
> Gesendet: Donnerstag, 30. Januar 2014 12:41
> 
> > $ ptxdist print PACKAGES-y
> > For the corresponding URL I think you will need a script which queries each package's URL one by one.
> 
> That’s fine, thank you.

Actually, correct is:
$ ptxdist print PACKAGES

There are also HOST_PACKAGES, CROSS_PACKAGES and LAZY_PACKAGES

> Is it possible to run a script with all the make variable visible in the
> environment? Running ptxdist print again for each var ist extremely slow..

If its just a few, then you can print them all at once:

$ ptxdist print-PACKAGES print-HOST_PACKAGES print-CROSS_PACKAGES print-LAZY_PACKAGES

It's not nice, because you need to count the lines.

If you're working in a specific BSP, you can also define a custom make
target in BSP/rules/post/<something>.make, do your stuff there and call it
with "ptxdist make <whatever>"

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2014-01-30 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 11:24 Bernhard Bender
2014-01-30 11:40 ` Juergen Beisert
2014-01-30 13:58   ` Bernhard Bender
2014-01-30 19:31     ` Michael Olbrich [this message]

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=20140130193159.GB3223@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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