From: Romain Naour <romain.naour@smile.fr>
To: Thierry Bultel <thierry.bultel@linatsea.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] candidate packages : ros2 and wxwidgets
Date: Wed, 5 Jan 2022 15:32:52 +0100 [thread overview]
Message-ID: <21546798-75a4-c7ef-6b80-420bf5b516d8@smile.fr> (raw)
In-Reply-To: <5be78f0b-fdb2-66a0-71a1-11538c064148@linatsea.fr>
Le 05/01/2022 à 14:49, Thierry Bultel a écrit :
>> We also have some companies interested by ROS2 but they are using meta-ros Yocto
>> layer.
>>
>
> That would be therefore of less interest to them, unless they are thinking of
> switching to buildroot.
Well, I guess they use Yocto by default since there is currently no other choice.
> In my case, I rather see companies that just start to enter in "the embedded
> world" but already use ROS(1/2) on desktops,
> so it is still not to late for them to make the good choice.
ROS is definitely not an easy framework to package into Buildroot, it's doable
but requires a lot of work and time.
Best regards,
Romain
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-05 14:33 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 [this message]
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=21546798-75a4-c7ef-6b80-420bf5b516d8@smile.fr \
--to=romain.naour@smile.fr \
--cc=buildroot@buildroot.org \
--cc=thierry.bultel@linatsea.fr \
/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.