On 09/22/2012 05:15 PM, Luca Barbato wrote:
> On 09/03/2012 10:54 PM, 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).
> Complain to cmake devs, hopefully they might come up with a solution.
> (the alternative is provide a clean autotools-based build system and ask
> upstream to please keep both. Usually works nice to cover all bases and
> make all people happy ^^;
It's a matter of 15minutes work to patch a cmake build system to allow
installation of both.
You can let cmake rename targets, so you have target library "foo" and
"foostatic", but the latter will be renamed to "foo" as well.