From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC] Xenomai examples repository
Date: Thu, 30 Nov 2006 19:12:52 +0100 [thread overview]
Message-ID: <1164910373.4952.34.camel@domain.hid> (raw)
In-Reply-To: <456E122F.5030406@domain.hid>
On Thu, 2006-11-30 at 00:05 +0100, Jan Kiszka wrote:
[...]
> To give it a start (and finally establish the infrastructure), I
> copied/reformatted some existing examples and created a simple,
> self-contained build system around them. The directory structure would
> be as I suggested:
>
> /examples/native/...
> /examples/posix/...
> /examples/...
> /examples/rtdm/generic/...
> /examples/rtdm/serial/...
> /examples/rtdm/...
>
> I derived a generic Makefiles from my own one for tests (which was in
> turn derived from previous work by Hannes Mayer). It can compile a given
> list of user space applications and kernel modules (2.4 and 2.6)
The 2.4 section looks x86-dependent. Compiling out-of-tree modules with
2.4 over ppc would require a bit more magic to find the actual flags
needed.
> against
> some Xenomai installation (make XENO=..., unless xeno-config is already
> in $PATH) or a Xenomai-kernel (make KSRC=...). Moreover, there is simple
> Makefile under /examples just to kick building/cleaning of all subdirs
> at once.
>
> If it's OK for everyone, I would check this into trunk. We could then
> migrate existing demo code and snippets over and add new stuff as it
> pops up, both hopefully with the help of interested users.
Ok, let's merge this.
--
Philippe.
next prev parent reply other threads:[~2006-11-30 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 10:43 [Xenomai-core] [RFC] Xenomai examples repository Jan Kiszka
2006-11-29 18:28 ` Philippe Gerum
2006-11-29 23:05 ` Jan Kiszka
2006-11-30 18:12 ` Philippe Gerum [this message]
2006-11-30 18:18 ` Jan Kiszka
2006-11-30 18:23 ` 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=1164910373.4952.34.camel@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.