All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@smile.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Thierry Bultel <thierry.bultel@linatsea.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] candidate packages : ros2 and wxwidgets
Date: Wed, 5 Jan 2022 14:40:47 +0100	[thread overview]
Message-ID: <5d0600a1-eb8c-8d69-cf9a-fee4fbca0c73@smile.fr> (raw)
In-Reply-To: <20220105142924.4b11ed83@windsurf>

Hello,

Le 05/01/2022 à 14:29, Thomas Petazzoni a écrit :
> Hello Thierry,
> 
> On Wed, 5 Jan 2022 10:46:46 +0100
> Thierry Bultel <thierry.bultel@linatsea.fr> wrote:
> 
>> 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.

We also have some companies interested by ROS2 but they are using meta-ros Yocto
layer.

>>
>> 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 ?
> 
> These packages would certainly be very welcome. ROS2 especially makes a
> lot of sense.
> 
> Some prior work:
> 
>   https://github.com/mchalain/br_ros
>   http://lists.busybox.net/pipermail/buildroot/2019-March/246497.html

This is for ROS (v1), this series must be reworked for ROS2.

Marc had no time for cleaning and upstreaming this series :-/

> 
> I'll be happy to help in the review of such packages.

Same here, I'll try to help.

Best regards,
Romain

> 
> Best regards,
> 
> Thomas
> 

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

  reply	other threads:[~2022-01-05 13:40 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 [this message]
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

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=5d0600a1-eb8c-8d69-cf9a-fee4fbca0c73@smile.fr \
    --to=romain.naour@smile.fr \
    --cc=buildroot@buildroot.org \
    --cc=thierry.bultel@linatsea.fr \
    --cc=thomas.petazzoni@bootlin.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.