From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Yocto
Date: Sun, 10 Sep 2017 21:16:52 +0200 [thread overview]
Message-ID: <20170910191652.g3h4q4oeepi4sbwo@pengutronix.de> (raw)
In-Reply-To: <2267308.8Ft4I4ybYW@hydra>
On Sat, Sep 09, 2017 at 08:36:13PM +0200, Tim Sander wrote:
> I really would like to use ptxdist for my next private project where i
> would like to try ROS.
ROS1 or ROS2?
> As far as i see, its already packaged for OpenEmbedded or Angstrom.
I only know of old ROS packages made by the BMW folks, but this is
neither current versions of ROS, nor ROS2. Do you know of newer code?
> 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.
We started with ptxdist packaging for ROS2 two techweeks ago, but it is
a slow process if you have only one week per year. If someone would be
interested commercially, it would probably be possible to get a solution
faster, bug that didn't happen so far.
> 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 :-(.
Do you have logfiles for the fails? We are doing a lot of test builds
here, and if something breaks, we would like to know.
rsc
--
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
next prev parent reply other threads:[~2017-09-10 19:16 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
2017-09-10 19:16 ` Robert Schwebel [this message]
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=20170910191652.g3h4q4oeepi4sbwo@pengutronix.de \
--to=r.schwebel@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