From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Yocto
Date: Sat, 09 Sep 2017 18:33:03 +0200 [thread overview]
Message-ID: <1504974783.21495.404.camel@erwinrol.com> (raw)
In-Reply-To: <9f286cd2-e9cb-21fa-e0e3-c1e7107e1a05@gr13.net>
Hey all,
On Sat, 2017-09-09 at 17:54 +0200, Enrico Weigelt, metux IT consult
wrote:
> On 09.09.2017 15:03, Erwin Rol wrote:
> > but I was wondering if there are > ppl that made usecase comparisons between ptxdist and Yocto? My personal
>
> I'm currently in process of bringing up a board, where the vendor
> only supplied an image built via yocto (based on an phycore-imx6,
> so they just phycore's repos).
Exactly my problem, Yocto is becoming the Ubuntu of embedded Linux, and
like Ubuntu not everything is good about it. But vendors like Intel,
Xilinx, TI, etc. don't even know ptxdist exists, they all only offer
some Yocto layers.
> Finding out what kernel and bbx trees it uses, and the exact configs,
> and how to images are built, turned out to be quite time consuming.
Yeah the learning curve is steep, but that should not be a show stopper.
> And the whole bitbake machinery is really slow.
Over all I don't think bitbake is much slower than ptxdist, when
building from 0 to 100%.
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) :-/
- Erwin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-09 16:33 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 [this message]
2017-09-10 19:24 ` Enrico Weigelt, metux IT consult
2017-09-10 20:09 ` Erwin Rol
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=1504974783.21495.404.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