| 1 |
On Thu, 2017-11-16 at 14:48 +0100, Michał Górny wrote: |
| 2 |
> // NB: I'm not sure if I haven't submitted it already but that was |
| 3 |
> // a long time ago, so let's try again. Requested by soap. |
| 4 |
> |
| 5 |
> The out-of-source.eclass is a simple multilib-minimal-style wrapper |
| 6 |
> to perform out of source builds of autotools (and other) packages. It |
| 7 |
> is |
| 8 |
> mostly derived from the function served in the past by autotools- |
| 9 |
> utils |
| 10 |
> since a number of developers found it useful. However, in order to |
| 11 |
> avoid |
| 12 |
> the mistakes of autotools-utils, it is meant to be focused on a |
| 13 |
> single |
| 14 |
> feature and have a better API. |
| 15 |
> |
| 16 |
> This eclass has two use cases: |
| 17 |
> |
| 18 |
> 1. Ensuring that packages are tested with out-of-source builds. |
| 19 |
> |
| 20 |
> 2. Improving consistency between multilib and non-multilib packages. |
| 21 |
> |
| 22 |
> In the most basic form, it just redefines the phases from |
| 23 |
> src_configure() |
| 24 |
> to src_install() with out-of-source wrappers. However, each phase can |
| 25 |
> be overriden using my_src_*() sub-phase that is run inside build dir |
| 26 |
> (alike multilib_src_*() in multilib-minimal). There is also |
| 27 |
> my_src_install_all() for the trailing source-dir actions. |
| 28 |
|
| 29 |
+1 |
Archives