On 09/22/2012 05:25 PM, hasufell wrote:
> add_library(foostatic STATIC foo.cpp foo.h)
> set_target_properties(foostatic PROPERTIES OUTPUT_NAME foo)
> add_library(foo SHARED foo.cpp foo.h)
Looks a bit kludgy but should work well as a macro, willing to contact
upstream and/or ask cmake devs to incl
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
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
On Thursday 06 of September 2012 10:18:34 Brian Harring wrote:
> 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?
> > >
> > >
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
>
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 cont
On 28/08/2012 15:36, Mart Raudsepp wrote:
> static-libs is for installing static libraries IN ADDITION to shared
> libraries, not instead.
> USE=static is for what you have in mind there.
PE is not the same as ELF so on Windows you either build one or the
other for a number of reasons.
Now on a d
On N, 1970-01-01 at 00:00 +, Gregory M. Turner wrote:
> On 8/28/2012 1:09 AM, Michał Górny wrote:
> > On Tue, 28 Aug 2012 02:15:40 +0200
> > hasufell wrote:
> >> static-libs
> > pointless
>
> I have to mask this flag for dev-libs/{gmp,mpc} in my cygwin overlay,
> where one can have static or
On 8/28/2012 1:09 AM, Michał Górny wrote:
On Tue, 28 Aug 2012 02:15:40 +0200
hasufell wrote:
static-libs
pointless
I have to mask this flag for dev-libs/{gmp,mpc} in my cygwin overlay,
where one can have static or dynamic, but not both, as per. upstream
requirements (no idea why). So FTR,
On Tue, 28 Aug 2012 02:15:40 +0200
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?
Some people believe that IUSE=st
On Tue, 2012-08-28 at 02:15 +0200, 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?
For example, static linking is dis
On 27/08/2012 17:15, hasufell wrote:
> Is there a reason not to support static-libs in an ebuild if the package
> supports it?
Most libtool software "supports" static-libs, because libtool let you
build them, _but_ it might not be test or might not even work.
One example is software that relies o
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?
13 matches
Mail list logo
