All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Lenglet <rlenglet@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Cosmetic changes to script xeno-config + man page
Date: Tue, 18 Oct 2005 17:59:22 +0900	[thread overview]
Message-ID: <200510181759.22534.rlenglet@domain.hid> (raw)
In-Reply-To: <17236.37957.919219.175800@domain.hid>

> In order to compare Xenomai with other Debian packagees, I
> checked gtk-config, and I have a few remarks on xeno-config
> and its manpage.
[...]

I merely documented xeno-config as it is now, and made the 
printed usage consistent. If you modify it, I will update the 
manpage accordingly.


Another item to add to the looOOong-term wishlist: I would like 
to have ready-to-use autoconf rules, to use instead of 
xeno-config.

If someone ever writes such rules, e.g. in a "xenomai.m4" file, 
it would only be necessary, at Xenomai install time:
1- to copy xenomai.m4 into /usr/share/autoconf/autoconf/
2- to add the following line into autoconf.m4:
m4_include([autoconf/xenomai.m4])
2- to regenerate autoconf.m4f by running:
cd /usr/share/autoconf/autoconf
autom4te --language=autoconf --freeze --output=autoconf.m4f

A simpler solution would be to ship a xenomai.m4 to be used as a 
acinclude.m4 in every project using Xenomai. But I have had very 
bad experiences with aclocal in that use case. aclocal is quite 
buggy. And it would be more confortable for projects it is were 
immediately available after installing Xenomai.


> Now, about the manpage itself, unless I am wrong, the DESTDIR
> feature is not documented, it is very useful when compiling
> for a target.

DESTDIR is a feature of makefiles generated through Automake, not 
of xeno-config. Why would you like to document this is in 
xeno-config's manpage?

-- 
Romain Lenglet


  reply	other threads:[~2005-10-18  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-16 16:57 [Xenomai-core] Cosmetic changes to script xeno-config + man page Romain Lenglet
2005-10-17 16:33 ` Jim Cromie
2005-10-17 17:17   ` Romain Lenglet
2005-10-17 19:06     ` Gilles Chanteperdrix
2005-10-18  6:20     ` Gilles Chanteperdrix
2005-10-18  8:59       ` Romain Lenglet [this message]
2005-10-18 17:29         ` Gilles Chanteperdrix
2005-10-19  4:53           ` Romain Lenglet
  -- strict thread matches above, loose matches on Subject: below --
2005-10-19  7:37 Fillod Stephane
2005-10-19  7:47 ` Gilles Chanteperdrix
2005-10-19  8:15 Fillod Stephane
2005-10-19  8:42 ` Romain Lenglet

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=200510181759.22534.rlenglet@domain.hid \
    --to=rlenglet@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.