From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [PATCH] move RTDM headers
Date: Sat, 07 Jan 2006 18:23:37 +0100 [thread overview]
Message-ID: <43BFF919.60706@domain.hid> (raw)
In-Reply-To: <43BFF69C.4040705@domain.hid>
Jan Kiszka wrote:
> Philippe Gerum wrote:
>
>>Jan Kiszka wrote:
>>
>>
>>>Hi Philippe,
>>>
>>>this patches cleans up the include/rtdm folder by moving internal
>>>headers to ksrc/skins/rtdm, leaving only rtdm.h, rtdm_driver.h, the two
>>>profile headers, and syscall.h there. The latter is still only needed
>>>for building Xenomai itself, thus it will not be installed. Successfully
>>>built for 2.4 and 2.6. Additionally, I compiled latest RTnet SVN against
>>>it without problems (x86, PPC is currently being fixed by Wolfgang).
>>>
>>>Please apply/move the involved headers and run bootstrap.
>>>
>>
>>This one broke the build here:
>>
>>--
>> CC kernel/xenomai/skins/rtdm/core.o
>>kernel/xenomai/skins/rtdm/core.c:36:18: core.h: No such file or directory
>>kernel/xenomai/skins/rtdm/core.c:37:20: device.h: No such file or directory
>>--
>
>
> Updated your repos? As you forgot to apply the moving, I also got
> problems and applied my local versions of core.h, device.h, and proc.h,
> also removing the three from their previous location.
>
The problem is that the patch does not recreate those files in
ksrc/skin/rtdm, but only deletes them from include/rtdm.
>
>>Additionally, it's a really very bad idea to start including things like
>>"core.h" removing the rtdm/ prefix, while other include files like
>>nucleus/core.h exist. For the sake of readability, I'm going to revert
>>this particular change at least.
>>
>
>
> That's why I use #include "core.h", which -for me- clearly states: "Pick
> the local one!"
Nope, it "states pick the first one you find outside of the system dirs
depending on the order of the directories listed by -I in your
Makefile", which is quite different, and leads to all sort of
braindamage issues if you happen to screw up your CFLAGS in your Makefile.
You will now have to tweak the Makefiles again...
>
That's ok, I will do that. The prefix rule is enforced everywhere for
internal headers so that nobody gets mad trying to find why the wrong
one is included, and the best way not to depend on "-I" pecularities is
to avoid playing with them in the first place. Additionally, this leaves
no doubt about which header you wanted to include, regardless of the
sanity of your Makefile.
> Jan
--
Philippe.
next prev parent reply other threads:[~2006-01-07 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 12:22 [Xenomai-core] [PATCH] move RTDM headers Jan Kiszka
2006-01-07 13:41 ` [Xenomai-core] " Philippe Gerum
2006-01-07 13:46 ` Philippe Gerum
2006-01-07 17:07 ` Philippe Gerum
2006-01-07 17:13 ` Jan Kiszka
2006-01-07 17:23 ` Philippe Gerum [this message]
2006-01-07 17:54 ` Jan Kiszka
2006-01-07 18:15 ` Philippe Gerum
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=43BFF919.60706@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.