On Thu, Dec 15, 2016 at 6:25 PM, Philippe Gerum wrote:
> On 12/15/2016 05:16 PM, Ronny Meeus wrote:
>> On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum 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
On 12/15/2016 05:16 PM, Ronny Meeus wrote:
> On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum 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-
On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum 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 call
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
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
A check is alre
