[Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

Ronny Meeus ronny.meeus at gmail.com
Thu Dec 15 17:16:04 CET 2016

On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum <rpm at xenomai.org> wrote:
> On 12/15/2016 12:47 PM, Ronny Meeus wrote:
>> bootstrap.o is linked to the application code.
>> In case the execution of the static constructors is postponed
>> in the applicaion and the auto-init feature is used, the
>> xenomai_init is called 2 times:
>> - once in the path of the wrap_main
>> - later in the context of the static constructor
> Why do you keep the auto-init feature on, given that you already control
> the early init code by postponing the execution of the C++ ctors? I
> would rather expect something like:
> - build with no-auto-init
> - call xenomai_init() manually from your entry point to activate the
> Xenomai services when you see fit.
> - call the ctor init chain.

We have a lot of applications, some of them postpone the execution of
the constructors while others dont.
We were calling the init function ourselves before, but we would like to
remove this code to keep the application code cleaner and to have less
explicit dependencies.

Using the auto-init has advantages as well, one of them being that the
init code of xenomai can change completely transparant for the
application code.


> --
> Philippe.

More information about the Xenomai mailing list