From: Stefan Nickl <stefan.nickl@gmail.com>
To: Mike Davies <busybox_mail@rovoreed.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] candidate packages : ros2 and wxwidgets
Date: Tue, 10 Oct 2023 20:50:40 +0200 [thread overview]
Message-ID: <c604e3e874577b85498bac2c2ad4d6a25c7c9cf3.camel@gmail.com> (raw)
In-Reply-To: <b8ccd688c2c755964b5aff6ecfd7ff53a6c6e8fa.camel@rovoreed.com>
On Wed, 2022-06-29 at 15:29 +0100, Mike Davies wrote:
> I have spent many hours (over 100 so far) trying to get ROS2 built as
> part of buildroot. I have been using the recommended ROS source build
> route of using rosdep/colcon etc., to build ROS2 Galactic and more
> recently Humble
>
> Starting with buildroot-2022.02 I have had to add 41 new packages, and
> alter an existing 6 packages - either adding host builds or changing
> configuration options.
>
> So far I have managed to build 157 of the 340 odd components. I can get
> code onto the target, but it doesn't do a lot because so many
> components are missing.
>
> Alas, I have got to the stage where I think it is no longer possible to
> progress, or at least, it is going to take vastly more time than I am
> willing to take.
Hey Mike,
I just found this old thread and wondered if you could share the work
you've done so far.
I'm interested in using ROS2 in an embedded system with buildroot and
cross-compilation to aarch64. I don't need a full ros distribution,
just enable some basic C/C++ programs on the target to talk with other
ros nodes on the network via topics, services and actions.
Maybe having just a very stripped-down version of ROS2 in buildroot
would be useful for others as well.
Thanks,
Stefan
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-10-10 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 9:46 [Buildroot] candidate packages : ros2 and wxwidgets Thierry Bultel
2022-01-05 13:29 ` Thomas Petazzoni
2022-01-05 13:40 ` Romain Naour
2022-01-05 13:49 ` Thierry Bultel
2022-01-05 14:32 ` Romain Naour
2022-01-17 10:07 ` Marcus Folkesson
2022-01-07 21:35 ` Julien Olivain
2022-01-08 13:27 ` Arnout Vandecappelle
2022-06-29 14:29 ` Mike Davies
2023-10-10 18:50 ` Stefan Nickl [this message]
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=c604e3e874577b85498bac2c2ad4d6a25c7c9cf3.camel@gmail.com \
--to=stefan.nickl@gmail.com \
--cc=buildroot@buildroot.org \
--cc=busybox_mail@rovoreed.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.