[ptxdist] building a project using ptxdist sysroot-target

[ptxdist] building a project using ptxdist sysroot-target

[Jon Ringle]

[-- Attachment #1.1: Type: text/plain, Size: 756 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 882 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

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

[Matthias Klein]

[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]

We are also interested in building a "development package" for our 
platform which contains the compiler, library and header files to build 
and debug applications with QtCreator so that our application developers 
don't need to use / have ptxdist.


Any Tips in that direction would be fine.


Best regards,

Matthias

------ Originalnachricht ------
Von: "Jon Ringle" <jon@ringle.org>
An: ptxdist@pengutronix.de
Gesendet: 15.01.2014 16:31:46
Betreff: [ptxdist] building a project using ptxdist sysroot-target
>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

[-- Attachment #1.2: Type: text/html, Size: 2330 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

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