[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: installing config.h
From: |
Raja R Harinath |
Subject: |
Re: installing config.h |
Date: |
Wed, 04 Sep 2002 12:33:48 -0500 |
User-agent: |
Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu) |
Thien-Thi Nguyen <address@hidden> writes:
> Waldemar Rosenbach <address@hidden> writes:
>
> Is there another way to solve this kind of problem?
>
> well, it's not clean, but you can process the headers on install. this could
> be a provisional approach (i.e., kludge) while you make the interface platform
> independent.
>
> see below for petrify-headers. sample usage:
>
> install-data-hook:
> $(srcdir)/petrify-headers $(srcdir) $(pkginclude_HEADERS)
> files=`ls *.petrified | sed 's/.petrified$$//g'`; \
> for f in $$files ; do \
> $(INSTALL_DATA) $$f.petrified $(DESTDIR)$(pkgincludedir)/$$f ; done
> rm -f *.petrified ^^^^^^^^^^^^^^^^^^^^^^^^
That doesn't allow the same prefix to be used by multiple
architectures. For better or worse, $includedir and $pkgincludedir
are in $prefix, not in $exec_prefix. So, technically, they are meant
for arch-independent headers.
(To confound things, I think the FHS has /usr/include as
arch-dependent. So, what you have will be OK for a Linux packager who
uses $prefix=/usr.)
- Hari
--
Raja R Harinath ------------------------------ address@hidden