From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] lndir'ing sysroot-target
Date: Mon, 7 Nov 2011 08:48:40 -0500 [thread overview]
Message-ID: <CAMwGMjzErDfFURqUcP9dMsug98ns1B2qZA-oqCbAGm2CPd1KdQ@mail.gmail.com> (raw)
In-Reply-To: <20111107104907.GL20768@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1989 bytes --]
On Mon, Nov 7, 2011 at 5:49 AM, Michael Olbrich <m.olbrich@pengutronix.de>wrote:
> On Mon, Nov 07, 2011 at 11:15:23AM +0100, Erwin Rol wrote:
> > On 6-11-2011 20:10, Jon Ringle wrote:
> > >Something that I'd like to see is a way to have a kernel+initramfs image
> > >to be created as a package. As it stands now, I create a kernel platform
> > >image and a rootfs platform image, and because the rootfs image contains
> > >kernel modules not contained within the initramfs image, I end up having
> > >the kernel built twice with two separate kernel source trees that are
> > >basically the same.
> >
> > I have that with one project too. But that also boils down to
> > multiple images I guess, one hardisk rootfs and one ram rootfs.
>
> What are the requirements for these images?
>
> What we currently do to create images is:
> - take some ipkgs (currently all selected)
> - extract them to a tmpdir
> - create all selected images from this tmpdir
>
> If we expand this to do this multiple times for different sets of ipkgs and
> different images, would that cover your use-case?
>
>
In the case of kernel+initramfs, it would not be as simple as that, since
in my case the initramfs image is built using uclibc toolchain and rootfs
image is built with glibc toolchain. So, I may have busybox for initramfs
using uclibc and busybox for rootfs using glibc.
I was envisioning something along the lines of a "nested" ptx project for
the kernel+initramfs where kernel and packages for initramfs are built
using PTXCONF_COMPILER_PREFIX_KERNEL as the toolchain.
Menu to select packages for kernel+initramfs "nested" ptx project:
$ ptxdist initramfs menuconfig
The following would build all selected packages and if kernel+initramfs
package is selected then to build it, it would recurse into calling a
nested ptxdist to build the kernel+initramfs and set the nested
PTXCONF_COMPILER_PREFIX to the parent's PTXCONF_COMPILER_PREFIX_KERNEL as
the toolchain:
$ ptxdist go
$ ptxdist images
Jon
[-- Attachment #1.2: Type: text/html, Size: 2613 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2011-11-07 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 19:46 Erwin Rol
2011-11-05 10:04 ` Robert Schwebel
2011-11-05 11:23 ` Michael Olbrich
2011-11-06 0:37 ` Erwin Rol
2011-11-06 10:33 ` Michael Olbrich
2011-11-06 13:16 ` Erwin Rol
2011-11-06 14:40 ` Michael Olbrich
2011-11-06 19:10 ` Jon Ringle
2011-11-07 10:15 ` Erwin Rol
2011-11-07 10:49 ` Michael Olbrich
2011-11-07 13:48 ` Jon Ringle [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=CAMwGMjzErDfFURqUcP9dMsug98ns1B2qZA-oqCbAGm2CPd1KdQ@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