On 01/09/2017 20:40, Alex Turbov wrote:
Hi Robert,
On Fri, Sep 1, 2017 at 9:21 PM, Robert Dailey
mailto:rcdailey.li...@gmail.com>> wrote:
One problem I thought of with the former (one big target.cmake with
all import targets in there) is that if you only ask for a subset of
comp
I've started to use CMake a quite long time ago, and do not search for
"standards" or "guidelines" anymore %)
But I could mention some chapters in the official documentation (in the
"Reference Manuals" section) which are really full of "secret knowledge",
but the problem is that they are too compli
On Fri, Sep 1, 2017 at 1:40 PM, Alex Turbov wrote:
> Hi Robert,
>
>
> On Fri, Sep 1, 2017 at 9:21 PM, Robert Dailey
> wrote:
>>
>>
>> One problem I thought of with the former (one big target.cmake with
>> all import targets in there) is that if you only ask for a subset of
>> components in find_p
Hi Robert,
On Fri, Sep 1, 2017 at 9:21 PM, Robert Dailey
wrote:
>
> One problem I thought of with the former (one big target.cmake with
> all import targets in there) is that if you only ask for a subset of
> components in find_package(), you will still get all of them since all
> imports are d
First of all, I want to apologize for including the developer list.
Maybe I'm not being patient enough, but it seems like every post I've
made on the normal users list doesn't get any attention.
Secondly, the cmake-packages portion of the cmake documentation
doesn't go into a ton of detail about c
Suppose I have a library target and I setup a config package for it
and install target exports for it. What is the process for supporting
installation of the shared library and static library variants (maybe
the same answer applies to debug and release variants too)?
Should you create 1 target and
On Fri, Sep 1, 2017 at 9:41 AM, Gerhard Gappmeier <
gerhard.gappme...@ascolab.com> wrote:
> Hi Haocheng,
>
> `chcp` seems to be a Windows command.
> I'm talking about Linux, which is UTF-8 by default:
>
> $> locale
> LANG=en_US.utf8
> LC_CTYPE="en_US.utf8"
> LC_NUMERIC="en_US.utf8"
> LC_TIME="en_U
Hi Haocheng,
`chcp` seems to be a Windows command.
I'm talking about Linux, which is UTF-8 by default:
$> locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NA
Hi Gerhard,
On Fri, Sep 1, 2017 at 7:26 AM, Gerhard Gappmeier <
gerhard.gappme...@ascolab.com> wrote:
> hi all,
>
> just recently I discovered that our coverage builds on CDash don't work
> anymore.
> By analyzing the problem I found out that this is related to Ninja
> generator.
> I don't know w
hi all,
just recently I discovered that our coverage builds on CDash don't work
anymore.
By analyzing the problem I found out that this is related to Ninja
generator.
I don't know when the problem was introduced but it still exists with
CMake 3.9.1.
(GCC and gcov are version 4.9.4, but this is not
10 matches
Mail list logo