All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: jserv@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [SOLO] [PATCH] Obtain proper prefix for testsuite build
Date: Thu, 27 Mar 2008 01:03:37 +0100	[thread overview]
Message-ID: <47EAE459.90307@domain.hid> (raw)
In-Reply-To: <20080326143644.GB11244@domain.hid>

jserv@domain.hid wrote:
> Hello list,
> 
>   Currently, Xenomai/SOLO comes with testsuite for VxWorks emulation.
> The path to Xenomai/SOLO installation is fixed.  The patch attempts to
> obtain the proper prefix during build process.
> 
> Regards,
> -jserv
> 
> diff --git a/vxworks/testsuite/Makefile b/vxworks/testsuite/Makefile
> index 62430ff..13ca9a0 100644
> --- a/vxworks/testsuite/Makefile
> +++ b/vxworks/testsuite/Makefile
> @@ -1,4 +1,4 @@
> -SOLO := /usr/local/solo
> +SOLO := $(shell sed -n '/^prefix/'p ../Makefile | cut -c 9-)
>  XENO_CONFIG=$(SOLO)/bin/xeno-config
>  prefix := $(shell $(XENO_CONFIG) --prefix)
>

This won't work if you build out of the source tree like autoconf/automake
recommend, since it won't find the instantiated Makefile in the upper directory.
We could use an autoconf template to patch the prefix into
testsuite/Makefile.in, but the testsuite/ directory is meant to be movable and
compilable anywhere the user sees fit. This is basically why the Makefile has
not been autoconfiscated in the first place.

I guess we will have to leave with the "set your Xenomai install directory for
scripts and binaries in your PATH variable" rule. I have removed the absolute
SOLO prefix from the Makefile though, it was a left over from my development
environment.

Thanks for spotting this.

-- 
Philippe.


  reply	other threads:[~2008-03-27  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 14:36 [Xenomai-core] [SOLO] [PATCH] Obtain proper prefix for testsuite build jserv
2008-03-27  0:03 ` Philippe Gerum [this message]
2008-03-28 12:10   ` jserv

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=47EAE459.90307@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jserv@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.