All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: "xenomai" prefix in RTDM userspace includes
Date: Wed, 04 Jan 2006 15:54:28 +0100	[thread overview]
Message-ID: <43BBE1A4.1080902@domain.hid> (raw)
In-Reply-To: <43BBDA7D.3020600@domain.hid>

Jan Kiszka wrote:
> Hi,
> 
> the current RTDM profile headers (so far only rtserial.h and
> rtbenchmark.h) suffer from the "xenomai" prefix in the include path.
> This was introduced with 2.1. An example: rtserial.h contains "#include
> <xenomai/rtdm/rtdm.h>" which is fine in kernel space but requires that -
> in my eyes - ugly "xenomai"->"." link in the installation include dir.
> Moreover, it makes the RTDM profile headers Xenomai-specific (what they
> are not).
> 
> The orginal (but nowhere stated - yeah) idea was to always have a
> "rtdm/" dir in the include path whenever writing a RTDM driver or
> application for some supported environment. So I would rather like to
> see the Makefiles for Xenomai's RTDM drivers fixed in this regard,
> simply by adding
> 
> EXTRA_CFLAGS += -Iinclude/xenomai
> 
> This would allow to use the generic "#include <rtdm/rtdm.h>" in the
> profile headers again. Tweaking the Makefiles instead of the headers is
> also the way we handled this for drivers outside Xenomai (RTnet,
> rt_sja1000, ...).
> 
> Objections?
> 

None, provided we always keep on preventing naming conflicts. Prefixing 
with rtdm/ or xenomai/ does the job equally well.

> Jan
> 
> 
> PS: A cleanup of the RTDM userspace header installation is scheduled -
> only rtdm.h + the profile header will survive this.


-- 

Philippe.


      reply	other threads:[~2006-01-04 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 14:23 [Xenomai-core] "xenomai" prefix in RTDM userspace includes Jan Kiszka
2006-01-04 14:54 ` Philippe Gerum [this message]

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=43BBE1A4.1080902@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.org \
    /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.