From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist <ptxdist@pengutronix.de>
Subject: [ptxdist] Sharing host-* tools
Date: Thu, 06 Sep 2018 22:42:19 +0200 [thread overview]
Message-ID: <1536266539.8146.8.camel@erwinrol.com> (raw)
Hey all,
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.
- Erwin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-09-06 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 20:42 Erwin Rol [this message]
2018-09-07 7:04 ` Michael Olbrich
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=1536266539.8146.8.camel@erwinrol.com \
--to=mailinglists@erwinrol.com \
--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