All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Davies <busybox_mail@rovoreed.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] candidate packages : ros2 and wxwidgets
Date: Wed, 29 Jun 2022 15:29:48 +0100	[thread overview]
Message-ID: <b8ccd688c2c755964b5aff6ecfd7ff53a6c6e8fa.camel@rovoreed.com> (raw)
In-Reply-To: <2209e11a-bda9-5193-9b4d-20a5f0fa34e3@linatsea.fr>

On Wed, 2022-01-05 at 10:46 +0100, Thierry Bultel wrote:
> Hi,
> 
> For a number of companies, I can see a growing interest in having
> ros2 
> support in buildroot.
> Currently, people wanting to prototype (or make a product) a robotics
> applications, are stuck
> to either yocto, or, worse, to a desktop-like distribution.
> 
> 

I have only just stumbled across this thread.

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.

My latest problem is that ROS2 assumes Python complies with PEP3149 -
which is not entirely unreasonable since PEP3149 came out 12 years ago.
PEP3149 is an extension of PEP3147, and PEP3147 has been patched out of
the buildroot version of Python to save space. Alongside this there are
known problems cross compiling ROS2 - and following various threads it
appears that these problems have been known about for years. Try a
search for PYTHON_SOABI which appears related.

Should anyone need a robotics infrastructure, then MRPT might be an
answer. It took less than a day to get that up and running in
buildroot, but MRPT is less widely used.

I may continue with this port of ROS2. It has been educational - having
learnt a lot along the way, and probably more to learn, but I don't
think it's going to be possible without a lot of butchery to buildroot
& that may have implications for existing users.


> Another topic is charts displaying for sailing. The most famous 
> application (mostly used
> on raspberry by sailors) is OpenCpn, which is great but relies on
> wxWidgets.
> 
> Whereas I am looking for a sponsor for adding ros2 to buildroot, 
> (because it is a quite significant work,
> that implies to add a new build framework), I am thinking about using
> my 
> (little) free time for wxWidgets (and OpenCpn later).
> There has been an attempt is the past 
> (https://bugs.busybox.net/show_bug.cgi?id=261) but it does not
> seem to have lead to anything else since that time.
> 
> What are your thought about these both packages ? Any ideas, or links
> to 
> some WIP stuff ?
> 
> Best regards
> Thierry
> 
> -- 
> Re: test
> www.linatsea.fr <www.linatsea.fr>

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-06-29 14:37 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 [this message]
2023-10-10 18:50   ` Stefan Nickl

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=b8ccd688c2c755964b5aff6ecfd7ff53a6c6e8fa.camel@rovoreed.com \
    --to=busybox_mail@rovoreed.com \
    --cc=buildroot@buildroot.org \
    /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.