From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] building a project using ptxdist sysroot-target
Date: Thu, 16 Jan 2014 10:55:08 +0100 [thread overview]
Message-ID: <20140116095508.GA15269@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjyy_jBCui5O5ubDXE7GGhQJVf8ha2J6f_Adwffsjq+1xg@mail.gmail.com>
Hi,
On Wed, Jan 15, 2014 at 10:31:46AM -0500, Jon Ringle wrote:
> I've built a rootfs using ptxdist with PTXCONF_PROJECT_CREATE_DEVPKGS=y
> I now have in platform/packages/*-dev.tar.gz for each package built.
>
> I believe that I can use the *-dev.tar.gz files to recreate sysroot-target/
> so that a developer can build a project without using ptxdist that depends
> on libraries and include files that was built by ptxdist. Does this make
> sense?
>
> I'm looking at doing a workflow where ptxdist builds linux kernel and
> rootfs, and then the *-dev.tar.gz only are given to other developers to do
> their work of creating projects for the target board without having to
> build linux kernel and rootfs all over again.
>
> Is there support in ptxdist for this type of workflow model?
> Any other approaches that others have taken?
You can do that with PTXdist. Enable PROJECT_USE_DEVPKGS (this is right
next to PROJECT_CREATE_DEVPKGS) and set the path to the directory
containing the *-dev.tar.gz.
For any package with a matching *-dev.tar.gz PTXdist will skip all stages
including "install" and extract the archive instead. The rest
(copying the files to sysroot, targetinstall, etc.) happens as usual.
Note: just manually extracting the *-dev.tar.gz to create a sysroot will
not work. PTXdist does some magic to make sure the paths in any "*.la" etc.
match the new sysroot.
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
prev parent reply other threads:[~2014-01-16 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 15:31 Jon Ringle
2014-01-16 7:24 ` Matthias Klein
2014-01-16 9:55 ` 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=20140116095508.GA15269@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