Re: gnomes gtk+/glib fails VPATH install

[Gary V Vaughan <garyv aethos co uk>]

On Tue, Feb 17, 1998 at 11:36:53AM -0600, Raja R Harinath <Hari> wrote:
Hari> Both solutions are wrong for `glibconfig.h'.  `glibconfig.h' is the
Hari> output of the `configure' process, and will pretty surely be system
Hari> specific.  It is not right to install it under $(includedir).  In its
Hari> current form, it has to be installed under $(exec_prefix).

On Wed, Feb 18, 1998 at 09:59:05AM +0000, I <Gary> wrote:
Gary> That is a bug in Makefile.am, using the shipped Makefile.am
Gary> glibconfig.h will be installed to $(includedir) whether or not one of
Gary> my patches has been applied to automake. 
Gary> 
Gary> [snip]
Gary> 
Gary> But I think this would cause problems when $(exec_prefix) != $(prefix)
Gary> because nobody will have (eg) /usr/local/i586/include in their include
Gary> search path when using #include <glib.h> in thier own projects (which
Gary> is the point of installing the headers after all).

May I humbly retract the comments above? =)O|

It occurs to me that headers are implicitly architecture dependent anyway,
rendering this a non-issue.  I couldn't cross mount gcc headers from a
machine with different architecture and expect to be able to link against
them.  Similarly, if I run a cross compiler, I need a set of target headers
to link against, as the headers on my host machine are not expected to work.

Cheers,
	Gary V Vaughan
-- 
{#include #.signature#}
WARNING:  Cannot find '.signature' template file

PGP signature