From: Julien Blanc <julien.blanc@sprinte.eu>
To: "ruiqurm@gmail.com" <ruiqurm@gmail.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Issue with std::mutex when porting POSIX program to Xenomai 3
Date: Thu, 28 Mar 2024 08:24:51 +0000 [thread overview]
Message-ID: <4ef1b2532c41d19c57a1d0c6eb15f7c8aada8eba.camel@sprinte.eu> (raw)
In-Reply-To: <TYZPR04MB6425188BB84FE4C65883656BAA3B2@TYZPR04MB6425.apcprd04.prod.outlook.com>
Le jeudi 28 mars 2024 à 02:31 +0000, Sam Chiu a écrit :
>
> Thank you, Julien. I will give it a try.
>
> Additionally, I'm curious if, besides the issue with the mutex, you've encountered any significant challenges during the process
> of porting your POSIX program.
It was not a port, targetting xenomai was a requirement from the start of the projet, so i guess it makes things a lot easier. We
just learned that using any C++ standard synchronization/thread facilities is a no-go on xenomai. Since we already had some
higher-level facilities (we have some shared code that also targets freertos using this platform abstraction layer), it was pretty
easy for us.
Cobalt wrappers can be tricky sometimes, so we've learned to use __RT o __STD macros when needed (our apps are often a mixed bag
of RT and non-RT threads).
Regards,
Julien
next prev parent reply other threads:[~2024-03-28 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 2:31 Issue with std::mutex when porting POSIX program to Xenomai 3 Sam Chiu
2024-03-28 8:24 ` Julien Blanc [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-28 8:42 Sam Chiu
2024-03-26 9:13 Sam Chiu
2024-03-26 9:46 ` Julien Blanc
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=4ef1b2532c41d19c57a1d0c6eb15f7c8aada8eba.camel@sprinte.eu \
--to=julien.blanc@sprinte.eu \
--cc=ruiqurm@gmail.com \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).