RPM Community Forums

Mailing List Message of <rpm-devel>

Re: beecrypt include dir

From: Ralf S. Engelschall <rse+rpm-devel@rpm5.org>
Date: Mon 28 May 2007 - 21:54:46 CEST
Message-ID: <20070528195446.GA18909@engelschall.com>
On Mon, May 28, 2007, Ralf S. Engelschall wrote:

> On Mon, May 28, 2007, Olivier Thauvin wrote:
>
> > Le lundi 28 mai 2007, Jeff Johnson a écrit :
> > > > Do you agree with that ?
> > >
> > > In general, I believe that adjusting -I paths is superior to embedding
> > > partial relative structure within include paths as in
> > >      #include "beecrypt/beecrypt.h"
> >
> > BTW: I tried -Ibeecrypt but It seems -I want only absolute path :
>
> No, option -I always accepts also relative paths. Your problem might be
> more the fact that if you use -Ibeecrypt this works in the top-level
> directory of the source tree. But in a sub-directory it would have to
> be -I../beecrypt, etc. The solution is to use Autoconf's @top_srcdir@
> variable, i.e. place into Makefile.in -I@top_srcdir@/beecrypt

BTW, if you want to use CPPFLAGS as you don't want to change the
RPM sources at all, the usual indirect approach usually is to use
a construct like CPPFLAGS="-I`pwd`/beecrypt" and this way let the
particular absolute path be expanded dynamically.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com
Received on Mon May 28 21:58:40 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.