From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail-lb0-x22a.google.com ([2a00:1450:4010:c04::22a])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <jonringle@gmail.com>) 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 <ptxdist@pengutronix.de>; Wed, 15 Jan 2014 07:31:48 -0800 (PST)
MIME-Version: 1.0
Date: Wed, 15 Jan 2014 10:31:46 -0500
Message-ID: <CAMwGMjyy_jBCui5O5ubDXE7GGhQJVf8ha2J6f_Adwffsjq+1xg@mail.gmail.com>
From: Jon Ringle <jon@ringle.org>
Subject: [ptxdist] building a project using ptxdist sysroot-target
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=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

<div dir=3D"ltr"><div><div><div><div><div>I&#39;ve built a rootfs using ptx=
dist with PTXCONF_PROJECT_CREATE_DEVPKGS=3Dy<br></div>I now have in platfor=
m/packages/*-dev.tar.gz for each package built.<br><br></div>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?<br>
<br>I&#39;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.<br>
<br></div>Is there support in ptxdist for this type of workflow model?<br><=
/div>Any other approaches that others have taken?<br><br></div>Thanks,<br>J=
on<br></div>

--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==--