On Tue, 2 Apr 2013 13:47:07 +0200
Michał Górny <mgo...@gentoo.org> wrote:
[...]
> > - Header wrapping really has nothing to do with autotools and I
> > strongly believe this should be moved to multilib-build.
>
> It will be when there's a safe, public API for it. Right now, it's too
> fragile.
>
The problem is that at the moment it prevents non autotools{/,-utils}
based packages to do the wrapping. If _autotools-multilib_wrap_headers
were in multilib-build, it'd be trivial to add header wrapping support
in multilib-minimal.
What exactly is the unsafe part of the API of this function ? You could
very well make it functional by replacing MULTILIB_WRAPPED_HEADERS by
arguments to the function and then it'd do what it's supposed to: wrap
headers from its arguments into a multilib-safe header, move the unsafe
headers to "${ED}"/tmp/multilib-include ; if this function is called,
then multibuild_merge_root "${ED}"/tmp/multilib-include
"${ED}"/usr/include
_must_ be called at the end of src_install.
It's a weird API but after all it's not supposed to be used by
everyone ;)
Alexis.
