Betreff: [ptxdist] building a project using ptxdist sysroot-target

I've built a rootfs using ptxdist with PTXCONF_PROJECT_CREATE_DEVPKGS= =3Dy
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 work= flow model?
Any other approaches that others have taken?

Thanks,
Jon

--------=_MBB265EE6F-08B0-4F8A-ACAA-3D80A35A62DC-- --===============2115708335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============2115708335==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ptx.hi.pengutronix.de ([2001:6f8:1178:2:5054:ff:fec0:8e10] ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W3jfI-0004tb-RL for ptxdist@pengutronix.de; Thu, 16 Jan 2014 10:55:08 +0100 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80) (envelope-from ) id 1W3jfI-00059F-Pk for ptxdist@pengutronix.de; Thu, 16 Jan 2014 10:55:08 +0100 Date: Thu, 16 Jan 2014 10:55:08 +0100 From: Michael Olbrich Message-ID: <20140116095508.GA15269@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] building a project using ptxdist 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-lb0-x22a.google.com ([2a00:1450:4010:c04::22a]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W3SRe-0004N6-Ih for ptxdist@pengutronix.de; Wed, 15 Jan 2014 16:31:55 +0100 Received: by mail-lb0-f170.google.com with SMTP id u14so925824lbd.29 for ; Wed, 15 Jan 2014 07:31:48 -0800 (PST) MIME-Version: 1.0 Date: Wed, 15 Jan 2014 10:31:46 -0500 Message-ID: From: Jon Ringle Subject: [ptxdist] building a project using ptxdist 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="===============1128934352==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============1128934352== Content-Type: multipart/alternative; boundary=001a11c38b1cbee02c04f00401b6 --001a11c38b1cbee02c04f00401b6 Content-Type: text/plain; charset=ISO-8859-1 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 --001a11c38b1cbee02c04f00401b6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I've built a rootfs using ptx= dist with PTXCONF_PROJECT_CREATE_DEVPKGS=3Dy

I now have in platfor= m/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 dev= eloper 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 a= nd 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 b= uild linux kernel and rootfs all over again.

Is there support in ptxdist for this type of workflow model?
<= /div>Any other approaches that others have taken?

Thanks,
J= on

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