mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Sharing host-* tools
Date: Fri, 7 Sep 2018 09:04:14 +0200	[thread overview]
Message-ID: <20180907070414.mjcncbbgk3tjnpu6@pengutronix.de> (raw)
In-Reply-To: <1536266539.8146.8.camel@erwinrol.com>

Hi,

On Thu, Sep 06, 2018 at 10:42:19PM +0200, Erwin Rol wrote:
> I am still trying to figure out a better way to share prebuild ptxdist
> projects, some ideas here on the mailing list where interesting but I
> have problems understanding how to apply them to my usecases.
> 
> Already just sharing the host-* tools/libs would be useful, and I do
> not see how I can do that. 
> 
> First lets assume I have 3 projects (A, B and C) and for this example
> they all use the same ptxdist version, but for the rest they have not
> much in common.
> 
> To build those 3 projects I will have to do "ptxdist images" in all 3
> project directories.
> 
> This will cause all host-* tools (like cmake, autoconf, fakeroot, etc)
> to be build 3 times, taking up a lot of time. 
> 
> Is there are way to prebuild all host-* tools and lets the projects
> A,B, and C use those prebuild host tools. A bit like the toolchain, 
> wich is also not build with every ptxdist project. 

For most host-tools dev packages/prebuild archives[1] should work.
Not all packages create such an archive because they need to be relocatable
for this to work. Autotools for example.

And you need to be carefull when you use this. The filename depends on the
version and kconfig options. And since ptxdist-2018.08.0 on the content of
the make and in files.
If you have other differences (e.g. patches) then this will break.

There is also the architecture string (I should remove that for host
packages). You could rename/symlink the files if necessary.


Michael

[1] https://www.ptxdist.org/doc/daily_work_section.html#using-pre-built-archives

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

  reply	other threads:[~2018-09-07  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 20:42 Erwin Rol
2018-09-07  7:04 ` Michael Olbrich [this message]
2018-09-07  9:24   ` Erwin Rol
2018-09-07  9:52     ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180907070414.mjcncbbgk3tjnpu6@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox