From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-iy0-f172.google.com ([209.85.210.172]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RNPZA-0006nr-55 for ptxdist@pengutronix.de; Mon, 07 Nov 2011 14:48:52 +0100 Received: by iaeo4 with SMTP id o4so7473467iae.31 for ; Mon, 07 Nov 2011 05:48:41 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20111107104907.GL20768@pengutronix.de> References: <4EB44121.2010107@erwinrol.com> <20111105112309.GH20768@pengutronix.de> <4EB5D6C9.7040605@erwinrol.com> <20111106103301.GJ20768@pengutronix.de> <4EB688C8.1060205@erwinrol.com> <20111106144029.GK20768@pengutronix.de> <4EB7AFBB.8080304@erwinrol.com> <20111107104907.GL20768@pengutronix.de> Date: Mon, 7 Nov 2011 08:48:40 -0500 Message-ID: From: Jon Ringle Subject: Re: [ptxdist] lndir'ing sysroot-target Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1987929385==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============1987929385== Content-Type: multipart/alternative; boundary=bcaec529a051045b0b04b12550c7 --bcaec529a051045b0b04b12550c7 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Nov 7, 2011 at 5:49 AM, Michael Olbrich 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 --bcaec529a051045b0b04b12550c7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
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+initr= amfs image
> >to be created as a package. As it stands now, I create a kernel pl= atform
> >image and a rootfs platform image, and because the rootfs image co= ntains
> >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?

<= br>
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 toolch= ain.

Menu to select packages for kernel+initramfs "nest= ed" 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 calli= ng a nested ptxdist to build the kernel+initramfs and set the nested PTXCON= F_COMPILER_PREFIX to the parent's PTXCONF_COMPILER_PREFIX_KERNEL as the= toolchain:
$ ptxdist go
$ ptxdist images

Jon
--bcaec529a051045b0b04b12550c7-- --===============1987929385== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1987929385==--