| 1 |
On Tue, 2 Apr 2013 13:47:07 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
[...] |
| 4 |
> > - Header wrapping really has nothing to do with autotools and I |
| 5 |
> > strongly believe this should be moved to multilib-build. |
| 6 |
> |
| 7 |
> It will be when there's a safe, public API for it. Right now, it's too |
| 8 |
> fragile. |
| 9 |
> |
| 10 |
|
| 11 |
The problem is that at the moment it prevents non autotools{/,-utils} |
| 12 |
based packages to do the wrapping. If _autotools-multilib_wrap_headers |
| 13 |
were in multilib-build, it'd be trivial to add header wrapping support |
| 14 |
in multilib-minimal. |
| 15 |
|
| 16 |
What exactly is the unsafe part of the API of this function ? You could |
| 17 |
very well make it functional by replacing MULTILIB_WRAPPED_HEADERS by |
| 18 |
arguments to the function and then it'd do what it's supposed to: wrap |
| 19 |
headers from its arguments into a multilib-safe header, move the unsafe |
| 20 |
headers to "${ED}"/tmp/multilib-include ; if this function is called, |
| 21 |
then multibuild_merge_root "${ED}"/tmp/multilib-include |
| 22 |
"${ED}"/usr/include |
| 23 |
_must_ be called at the end of src_install. |
| 24 |
|
| 25 |
It's a weird API but after all it's not supposed to be used by |
| 26 |
everyone ;) |
| 27 |
|
| 28 |
Alexis. |
Archives