libqof variables in configure.in (Fwd: gentoo ebuild)

[Martin Klaffenboeck]

Am Mittwoch, den 11.01.2006, 11:27 +0100 schrieb Christian Stimming:
> > I'm concerned that:
> > 
> >   make install prefix=/tmp/dir/usr
> > 
> > .. will cause the program to rewrite the configuration file to look in
> > /tmp/dir/usr/bin when really /tmp/dir is just a temporary location for
> > the package management system to put the files until it can get
> > packaged and then installed into /usr/bin..
> 
> [...]
> In other words, the rule for qsf-dir.h triggers at "make all" and it 
> will definitely not trigger again on "make install". So the proposed 
> patch is not affected by that concern. In general this concern stays 
> perfectly valid and should be checked for always.

I'm not really sure how gnucash-svn handles this, but as far as I know
many applications work this way:

./configure creates a config.h which has all this variables inside,
where a c programm has to know a static path.  So inside of config.h
would stay your QSF_STATIC_PATH_VARIABLE defined.  Now make or make
install do not rewrite the config.h file, (just if it has to reconfigure
because of any changes in the configure script or configure.in, so as if
you don't use ./autogen.sh and ./configure before make, and make hast do
to this), so we have a consitent config.h file.  because make and make
install do not change this, the path will be ok, there is no recompile
of the application on make install prefix=/some/where

Am I right?

Martin