From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtprelay02.ispgateway.de ([80.67.31.25]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RNVFR-0005mh-D9 for ptxdist@pengutronix.de; Mon, 07 Nov 2011 20:52:51 +0100 Received: from [78.47.165.117] (helo=regiomontanus.bwalle.de) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1RNVFR-0001xX-4A for ptxdist@pengutronix.de; Mon, 07 Nov 2011 20:52:49 +0100 Date: Mon, 7 Nov 2011 20:52:47 +0100 From: Bernhard Walle Message-ID: <20111107195247.GA19701@regiomontanus.bwalle.de> References: <4EB31A2E.2000906@erwinrol.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4EB31A2E.2000906@erwinrol.com> Subject: Re: [ptxdist] ptxdist options help 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Hi, * Erwin Rol [2011-11-03 23:48]: > = > could someone explain the idea behind the following ptxdist options ? > = > Build Type (development) > [ ] use pre-built production release > [ ] built on top of another platform Don't know about that options, but I'm also interested in the second two options. Hopefully somebody of the ptxdist gurus (Michael? J=FCrgen?) can comment if that's correct and answer my remaining questions: > [ ] create dev packages This option creates (in addition to the ipk packages that can be installed on the target and that are used to create the target image) for each package a PKGNAME_$HASH_$ARCH-dev.tar.gz (in platform-$PLATFORM/packages) that contains everything the packages installs, not only the subset that is selected by the package.mk. Especially it contains header files for libraries that are not on the target. So some kind of $package.deb + $package-dev.deb. This package can be used in this step: > [ ] use dev packages If a development package is available, then ptxdist uses the contents of the development package to package the ipk package and to build the sysroot. It doesn't compile the package from source. This even works if the source isn't available. One remaining question: What exactly is the checksum? Is it honoured in the process when ptxdist checks if it uses the development package instead of building it from source? The ptxdist sources are a bit hard to read in that area ... at least for me. ;) Wouldn't it make sense to include the version number of the package in the file name? Regards, Bernhard -- = ptxdist mailing list ptxdist@pengutronix.de