From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: [ptxdist] building a project using ptxdist sysroot-target
Date: Wed, 15 Jan 2014 10:31:46 -0500 [thread overview]
Message-ID: <CAMwGMjyy_jBCui5O5ubDXE7GGhQJVf8ha2J6f_Adwffsjq+1xg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 756 bytes --]
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?
Thanks,
Jon
[-- Attachment #1.2: Type: text/html, Size: 882 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-01-15 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 15:31 Jon Ringle [this message]
2014-01-16 7:24 ` Matthias Klein
2014-01-16 9:55 ` Michael Olbrich
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=CAMwGMjyy_jBCui5O5ubDXE7GGhQJVf8ha2J6f_Adwffsjq+1xg@mail.gmail.com \
--to=jon@ringle.org \
--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