All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Michel Hautbois <jean-michel.hautbois@veo-labs.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xenomai 3.x
Date: Wed, 5 Oct 2016 14:59:18 +0200	[thread overview]
Message-ID: <CAH-u=81O5-WK-JDN5T+X7p7dYjaTPMjCKV1pLjfzLA5vnqj+Wg@mail.gmail.com> (raw)
In-Reply-To: <20161005145655.31cf0349@free-electrons.com>

Hi Thomas,

2016-10-05 14:56 GMT+02:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Hello,
>
> On Wed, 5 Oct 2016 14:41:08 +0200, Jean-Michel Hautbois wrote:
>
>> Right now, I am still hesitating, as I can have one xenomai.mk file
>> which would be pretty much the same for Cobalt, but needs some
>> modifications for Mercury. And you get a lot of ifeq() statements
>> which is not nice.
>> Or, having one xenomai-2.mk and one xenomai-3.mk (or anything similar).
>> Or, having one xenomai.mk which would support Xenomai 2.x and Xenomai
>> 3.x Cobalt only, and one xenomai-mercury.mk which would add support
>> for mercury options.
>
> For now, I think you should just start with a package/xenomai3/ package
> that handles all aspects of Xenomai 3 (i.e Cobalt and Mercury). Once
> you have something working, we can see what it looks like, and discuss
> whether merging with xenomai.mk is appropriate or not.
>
> What do you think about such an approach?

Sounds good.
See you in Berlin :) !

JM

  reply	other threads:[~2016-10-05 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  7:07 [Buildroot] Xenomai 3.x Jean-Michel Hautbois
2016-10-05  7:54 ` jerry at chordia.co.uk
2016-10-05  8:31   ` Jean-Michel Hautbois
2016-10-05 10:05     ` jerry at chordia.co.uk
2016-10-05 12:41       ` Jean-Michel Hautbois
2016-10-05 12:56         ` Thomas Petazzoni
2016-10-05 12:59           ` Jean-Michel Hautbois [this message]
2016-10-05  7:55 ` Thomas Petazzoni
2016-10-05  8:30   ` Jean-Michel Hautbois
2016-10-05 22:54     ` Arnout Vandecappelle
     [not found]       ` <CAH-u=81T3HDse2T0kTttcLmXO-OEFs-TifmQHB-DB=-kyBWpCw@mail.gmail.com>
     [not found]         ` <CAH-u=83inyC8cYX=ovP839-C0zARrTuvHC_FMG6igHEY8ZUDGw@mail.gmail.com>
     [not found]           ` <CAH-u=80w=DhdBd00D=TdQ=GKsh_wjZhJS5dyOokEzOgVoNuOKg@mail.gmail.com>
     [not found]             ` <CAH-u=83sffpomqzQbCpBe=iTHA78vyPSj_+-pidpAHQ2u6vZMQ@mail.gmail.com>
     [not found]               ` <CAH-u=82g7aXEVbe8zqqKvcR4vEH5HKwvPML+BPy+fk51-6gc3A@mail.gmail.com>
2016-10-06  5:34                 ` Jean-Michel Hautbois
2016-10-06  9:01                   ` Arnout Vandecappelle
2016-10-07  8:03                     ` Jean-Michel Hautbois
2016-10-07 12:06                     ` Thomas Petazzoni

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='CAH-u=81O5-WK-JDN5T+X7p7dYjaTPMjCKV1pLjfzLA5vnqj+Wg@mail.gmail.com' \
    --to=jean-michel.hautbois@veo-labs.com \
    --cc=buildroot@busybox.net \
    /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.