From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7B862138010 for ; Sat, 22 Sep 2012 15:26:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C029121C03F; Sat, 22 Sep 2012 15:25:57 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 01F7021C01D for ; Sat, 22 Sep 2012 15:25:15 +0000 (UTC) Received: from [192.168.4.5] (blfd-4d086c64.pool.mediaWays.net [77.8.108.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hasufell) by smtp.gentoo.org (Postfix) with ESMTPSA id 247B233C5AF for ; Sat, 22 Sep 2012 15:25:14 +0000 (UTC) Message-ID: <505DD857.6040207@gentoo.org> Date: Sat, 22 Sep 2012 17:25:11 +0200 From: hasufell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.7) Gecko/20120908 Thunderbird/10.0.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] supporting static-libs References: <503C0DAC.8050207@gentoo.org> <201209032254.15788.reavertm@gmail.com> <505DD5F5.9040305@gentoo.org> In-Reply-To: <505DD5F5.9040305@gentoo.org> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: f895718c-3bb5-491e-9c2e-b74aacbc7a2b X-Archives-Hash: 6e56441a5c4e187039894455c85676e9 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 ^^; > > lu > 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. e.g.: add_library(foostatic STATIC foo.cpp foo.h) set_target_properties(foostatic PROPERTIES OUTPUT_NAME foo) add_library(foo SHARED foo.cpp foo.h)