Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: > Waldemar Rosenbach <[EMAIL PROTECTED]> 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 ------------------------------ [EMAIL PROTECTED]
