From: Erwin Rol <mailinglists@erwinrol.com>
To: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Yocto
Date: Sun, 10 Sep 2017 22:09:08 +0200 [thread overview]
Message-ID: <1505074148.21495.408.camel@erwinrol.com> (raw)
In-Reply-To: <544c43fa-d20c-bdf2-d4f5-160dcde0892e@gr13.net>
On Sun, 2017-09-10 at 21:24 +0200, Enrico Weigelt, metux IT consult
wrote:
> On 09.09.2017 18:33, Erwin Rol wrote:
> > But when you want to do edit->compile->update iterations the "startup"
> > time for bitbake seems to be a killer. With ptxdist I just call
> > "./ptxdist compile bla" and I have no noticeable delay compared to
> > native compiling. That is something I extensively use with ptxdist, and
> > for Yocto that doesn't work (at least I don't know how) :-/
>
> Exactly. I need incremental builds almost all the day, so yocto would
> just slow me down by magnitudes.
>
> At that point I really wonder whether there's some really good pro
> argument that might compensate that big con.
I think Yocto assumes you develop your applications with the exported
SDK and than just build a final distribution when the application is
stable. The work flow seems very different from ptxdist. A bit like you
don't rebuild Redhat to test a linux program.
- Erwin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-10 20:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 13:03 Erwin Rol
2017-09-09 15:54 ` Enrico Weigelt, metux IT consult
2017-09-09 16:33 ` Erwin Rol
2017-09-10 19:24 ` Enrico Weigelt, metux IT consult
2017-09-10 20:09 ` Erwin Rol [this message]
2017-09-09 18:36 ` Tim Sander
2017-09-10 19:16 ` Robert Schwebel
2017-09-12 18:42 ` Tim Sander
2017-09-12 20:12 ` Robert Schwebel
2017-09-12 21:33 ` Tim Sander
2017-09-13 5:42 ` Robert Schwebel
2017-09-13 15:38 ` Michael Olbrich
2017-09-14 22:44 ` Tim Sander
2017-09-15 6:47 ` Michael Olbrich
2017-09-15 11:02 ` Alm, Michael
2017-09-16 9:25 ` Michael Olbrich
2017-09-10 19:13 ` Robert Schwebel
2017-09-11 9:25 ` Guillermo Rodriguez Garcia
2017-09-12 10:49 ` Alexander Dahl
[not found] <20170911063001.A6FE73EC2A2E_9B62D69B@mail.eckelmann.de>
2017-09-11 7:14 ` Schenk, Gavin
2017-09-12 10:44 ` Alexander Dahl
2017-09-12 13:29 ` Schenk, Gavin
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=1505074148.21495.408.camel@erwinrol.com \
--to=mailinglists@erwinrol.com \
--cc=enrico.weigelt@gr13.net \
--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