Re: [gentoo-dev] supporting static-libs

[Brian Harring <ferringb@gmail.com>]

On Mon, Sep 03, 2012 at 10:54:15PM +0200, Maciej Mrozowski wrote:
> On Tuesday 28 of August 2012 02:15:40 hasufell wrote:
> > Is there a reason not to support static-libs in an ebuild if the package
> > supports it?
> > 
> > It seems some developers don't care about this option. What's the gentoo
> > policy on this? Isn't this actually a bug?
> 
> A little remark.
> For CMake controlled buildsystem (as you're coming here from latest dev-
> games/simgear), there's no automatic way of building both static and shared 
> libs (simgear allows to choose just one).
> This is why I removed static libs support that you proposed for dev-
> games/simgear (similar to ruby eclass abi handling - manually calling phases 
> twice to build package 1st as shared, 2nd time as static).
> This is what I called "not worth the effort" in private discussion with you, 
> not quite "I don't care for static libs" :)

Guessing in the worst case, you can do a double compile to get around 
this, no?  And yes, that's freaking horrible, just verifying cmake 
isn't doing something special that blocks it.

Is upstream doing anything about this, or is it not on their 
radar/list-of-things-they-care-about ?

~harring