On Mon, Nov 07, 2011 at 08:52:47PM +0100, Bernhard Walle wrote:
> > [ ] 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?
The hash ist the md5sum of all selected options for the package, more or
less this:
grep PTXCONF_.*= | md5sum
PTXdist looks for: dev.tar.gz
It does not detect any changes to the patches (I tried that, it doesn't
perform well) or the makefile (other than the version), so don't change
anything there that will change the output of the install stage.
You can keep differnt versions of the same package in one pool, but I would
not recommend to put packages of different ptxdist versions in one pool
unless you've carefully reviewed all changes.
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- |
--
ptxdist mailing list
ptxdist@pengutronix.de
