| 1 |
On 07/17/2010 01:53 PM, Maciej Mrozowski wrote: |
| 2 |
> After gathering some feedback, after addressing reported issues, now I feel |
| 3 |
> it's ready for public consumption. especially when static-libs is being used |
| 4 |
> more and more often. It's purpose is to become standard eclass for autotools |
| 5 |
> build systems. |
| 6 |
> |
| 7 |
> Brief description: |
| 8 |
> autotools-utils.eclass is autotools.eclass (so libtool.eclass) and base.eclass |
| 9 |
> (so eutils.eclass) wrapper providing all inherited features (it is guaranteed, |
| 10 |
> no need to additionally inherit any of those) along with econf arguments as |
| 11 |
> Bash array, out of source build with overridable build dir location, static |
| 12 |
> archives handling, libtool files removal, enable/disable debug handling. It's |
| 13 |
> modelled after cmake-utils and resembles it in many aspects for consistency. |
| 14 |
> |
| 15 |
|
| 16 |
Maybe choose some other name. For me -utils in an eclass name means a |
| 17 |
set of helper functions. I would name it so the name reflects that it's |
| 18 |
meant to be used as the main build system provider. |
| 19 |
|
| 20 |
Regards, |
| 21 |
Petteri |
Archives