Le lundi 28 mai 2007, Ralf S. Engelschall a écrit :
> 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.

The problem is not with internal beecrypt, but with system one, aka how to 
find in simple way it is in {/usr/,/usr/local/}beecrypt, ans so set dir.
Notice all these path are in search path of gcc by default, so 
using "beecrypt/any.h" in code avoid to have to perform this detection.

But for now I am face to same issue python, but python includes header are in 
$include/python${python_ver}/ :\

But I will nuke that too ! :)