> If by pointer setup, you mean all the init stuff run by the various
> Xenomai libraries when called on behalf of xenomai_init(), then yes.
Perfect ! Then I will build that xeno_stub.so, dlopen() it and it will
be all fine....

Wait. Did I miss something ? I need to build and dlopen a stub shared
object in order to call something from bootstrap*.o ? Could I do that
directly by dlopening/calling the right shared object directly ?

It seems that __xenomai_init() calls many things from the setup list, in
multiple shared objects. So I would need to build another flavor of the
boilerplate: bootstrap.so, from witch I can call xenomai_init() directly
using python's ctypes. Does it look realistic ?

Also I wonder what happens to non-real-time threads witch have been
created before xenomai_init(). Is that safe if they are already running
threads using posix when xenomai_init() is called ? Should xenomai_int
be called before any thread is created ?

> The init sequence is explained here:
> http://xenomai.org/2015/05/application-setup-and-init/#Initialization_sequence
Seems like search engines never link to the real stuff. Many thanks.

--
Edouard


_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai

Reply via email to