From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Yocto
Date: Sat, 09 Sep 2017 20:36:13 +0200 [thread overview]
Message-ID: <2267308.8Ft4I4ybYW@hydra> (raw)
In-Reply-To: <1504962219.21495.392.camel@erwinrol.com>
Hi Erwin
Am Samstag, 9. September 2017, 15:03:39 CEST schrieb Erwin Rol:
> yes I know the topic is blasphemy ;-) but I was wondering if there are
> ppl that made usecase comparisons between ptxdist and Yocto? My personal
> experience with small systems (no GUI/X/wayland) is that ptxdist is
> really easy to get going. With large systems that need QT 5.9,
> webkitgtk/chromium, different OpenGL versions etc. is that ptxdist is
> not always that easy. But I am not experienced enough with Yocto to say
> if that will be easier/better.
>
> So hence the question, anybody out there that tried both and picked
> ptxdist (or yocto) for a reason ?
I really would like to use ptxdist for my next private project where i would
like to try ROS. As far as i see, its already packaged for OpenEmbedded or
Angstrom. But as it has its own build tools and lots of python module
dependencies it might be to much to get all this stuff build with ptxdist.
So i might go the OpenEmbedded road even if i have already a nice ptxdist
project for the Atlas board i am using. Btw. if some is interested in this
Atlas board ptxdist can publish it somewhere.
As for the speed i would say that one of my biggest gripes with ptxdist is
that -je16 -ji16 builds fail for me. And with that many virtual cores
available its realy a pitty :-(.
Best regards
Tim
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-09 18:39 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
2017-09-09 18:36 ` Tim Sander [this message]
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=2267308.8Ft4I4ybYW@hydra \
--to=tim@krieglstein.org \
--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