All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [ANNOUNCE] Xenomai Example Repository
Date: Sun, 03 Dec 2006 22:19:46 +0100	[thread overview]
Message-ID: <45733F72.8030209@domain.hid> (raw)
In-Reply-To: <45733E1D.8090605@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 3920 bytes --]

Wolfgang Grandegger wrote:
> Hi Jan,
> 
> Jan Kiszka wrote:
>> Wolfgang Grandegger wrote:
>>
>>> Jan Kiszka wrote:
>>>  
>>>> Wolfgang Grandegger wrote:
>>>>    
>>>>> Jan Kiszka wrote:
>>>>>      
>>>>>> Hi,
>>>>>>         the new Xenomai example repository has been created. I
>>>>>> don't want to
>>>>>>         repeat here what is explained already on the related wiki
>>>>>> page, please
>>>>>>         have a look at
>>>>>>             http://www.xenomai.org/index.php/Examples
>>>>>>         Instead, let me sketch what could be done next:
>>>>>>          o Port existing examples, snippets, demos from
>>>>>> ksrc/skins/* over, make
>>>>>>            them compilable and runnable if required.
>>>>>>          o Identify what kind of examples are lacking. You, the
>>>>>> user, is needed
>>>>>>            here. What do *you* think is missing, what would be
>>>>>> helpful to show?
>>>>>>          o Check what is needed to compile kernel-based examples
>>>>>> over PPC 2.4.
>>>>>>            Philippe indicated that some switches are likely
>>>>>> missing (x86 is fine
>>>>>>            already, other archs are 2.6-only).
>>>>>>         
>>>>> Some time ago I sent a patch for RTnet using the "kernel CFLAGS
>>>>>       capturing" trick to get proper switches for 2.4:
>>>>>      
>>>>> http://sourceforge.net/mailarchive/forum.php?thread_id=9493711&forum_id=24610
>>>>>
>>>>>             We could do the same trick here.
>>>>>       
>>>> Yeah, I had a look at this before. The point is that I would prefer to
>>>>     keep things _simple_ and self-contained. This capturing requires
>>>> some
>>>>     helper Makefile and complex call nestings that likely only
>>>> people with
>>>>     advanced make and shell skills can understand and adopt to their
>>>> projects.
>>>>     But maybe things are that complicated already, and this is just
>>>>     different complexity. How do you compile simple out-of-tree modules
>>>>     against 2.4 PPC kernels? Are there any standard flags? Or is it
>>>>     different for each board or each compiler version or whatever?
>>>>     
>>> I just cut and paste the flags from a kernel module make. For PPC,
>>> there are plenty of flags, not board but some are processor depended,
>>> but I'm unable to tell which one are really required. For this reason
>>> I like the module capturing trick.
>>>   
>> What about this patch? I /seems/ to work (yeah, only tested on
>> x86...), merging the
>> whole capturing stuff into the same Makefile. Please give it hell on PPC.
> 
> The attached Makefile works. I had to fix two problems. First, cross
> compilation was not supported. I now take the CC from "xeno-config --cc"
> for user space applications. I think "xeno-config" is intended only for
> making user space applications and therefore CC should be specified on
> the command line for kernel modules:
> 
> $ make KSRC=/devel/linuxppc_2_4_devel ARCH=ppc CC=ppc-linux-gcc

Yes, this is the intended usage. I also have to apply this here to build
against good-old gcc3 (looking forward to 2.4.34 supporting gcc4).

> ppc-linux-gcc -D__KERNEL__ -I/devel/linuxppc_2_4_devel/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -I/devel/linuxppc_2_4_devel/arch/ppc -fsigned-char
> -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -g
> -ggdb -DMODULE
> -I/devel/linuxppc_2_4_devel-2006_11_21_1134/include/xenomai
> -I/devel/linuxppc_2_4_devel-2006_11_21_1134/include/xenomai/compat
> -I/devel/linuxppc_2_4_devel-2006_11_21_1134/include/xenomai/posix    -c
> -o heartbeat-x86.o heartbeat-x86.c
> 
> Furthermore I removed "-I$(KSRC)/include", it is already included in the
> captured CFLAGS.

Good point.

Ok, I will merge these changes into all existing Makefiles and commit
the stuff "later".

Thanks,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

      reply	other threads:[~2006-12-03 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 10:24 [Xenomai-core] [ANNOUNCE] Xenomai Example Repository Jan Kiszka
2006-12-01 16:45 ` Wolfgang Grandegger
2006-12-01 17:22   ` Jan Kiszka
2006-12-01 17:54     ` [Xenomai-help] " Philippe Gerum
2006-12-01 22:47       ` Wolfgang Grandegger
2006-12-01 22:59         ` Philippe Gerum
2006-12-01 22:35     ` Wolfgang Grandegger
2006-12-03 14:53       ` Jan Kiszka
2006-12-03 21:14         ` Wolfgang Grandegger
2006-12-03 21:19           ` Jan Kiszka [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=45733F72.8030209@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=wg@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.