From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Cc: Robert Schwebel <r.schwebel@pengutronix.de>
Subject: Re: [ptxdist] Yocto
Date: Tue, 12 Sep 2017 20:42:26 +0200 [thread overview]
Message-ID: <2257468.zpI2h1gMCt@hydra> (raw)
In-Reply-To: <20170910191652.g3h4q4oeepi4sbwo@pengutronix.de>
On Sonntag, 10. September 2017 21:16:52 CEST Robert Schwebel wrote:
> 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?
I would like to have something not to dated. The website lists Lunar or
Kinetic Kame as versions...
> > 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?
This seems to be the repository for kinetic kame:
https://github.com/bulwahn/meta-ros/tree/kinetic-experimental
> > 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.
Well its my private tinkering project...
Do you have something i can build upon. I think one hurdle would be the custom
build system?
> > 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.
Strange, i think if i just do a build of DistroKit i can observe that make
just stops. I can restart it so a
for i in `seq 1 10`; do ptxdist -je16 -ji16 go; done;
Works faster than a normal build, so the failure is that not all packages are
getting build?
Best regards
Tim
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-12 18:42 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
2017-09-12 18:42 ` Tim Sander [this message]
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=2257468.zpI2h1gMCt@hydra \
--to=tim@krieglstein.org \
--cc=ptxdist@pengutronix.de \
--cc=r.schwebel@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