On Saturday 17 of July 2010 13:03:33 Petteri Räty wrote: > On 07/17/2010 01:53 PM, Maciej Mrozowski wrote: > > After gathering some feedback, after addressing reported issues, now I > > feel it's ready for public consumption. especially when static-libs is > > being used more and more often. It's purpose is to become standard > > eclass for autotools build systems. > > > > Brief description: > > autotools-utils.eclass is autotools.eclass (so libtool.eclass) and > > base.eclass (so eutils.eclass) wrapper providing all inherited features > > (it is guaranteed, no need to additionally inherit any of those) along > > with econf arguments as Bash array, out of source build with overridable > > build dir location, static archives handling, libtool files removal, > > enable/disable debug handling. It's modelled after cmake-utils and > > resembles it in many aspects for consistency. > > Maybe choose some other name. For me -utils in an eclass name means a > set of helper functions. I would name it so the name reflects that it's > meant to be used as the main build system provider.
It's for consistency with existing cmake-utils.eclass, which is main cmake buildsystem provider (no idea why it wasn't called just 'cmake' by initial commiters). Unfortunately autotools name is already taken and extending autotools so much (adding new defined phases) is not possible (nor is renaming) as far as I understand. -- regards MM
