The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14619
==
Reported By:nOOb3167
Assigned To:
===
On 12/02/2013 03:59 PM, Daniele E. Domenichelli wrote:
> For some reason a module containing something like
>
> function(_foo)
> [...]
> endfunction()
>
> macro(foo)
> _foo()
> endmacro()
>
> will cause an endless loop when calling foo() if the file is included in
> 2 different s
Hello Steve,
On 02/12/13 08:23, Stephen Kelly wrote:
> David Faure wrote:
>>> Configure step exited with non-zero code, assuming failure to configure
>>> for project kdelibs. Build step 'Execute shell' marked build as failure
>>
>> Looks like a bug in cmake_next, leading to infinite recursion and
On 11/27/2013 10:40 AM, Brad King wrote:
> Go ahead and merge it to 'next' for testing. I will review it
> there when I return from vacation next week.
Please extend the topic with updates to the test suite to cover the
new option. Even if it is too hard to test that the independent
build behavi
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14613
==
Reported By:Clinton Stimpson
Assigned To:
On 11/27/2013 12:19 PM, David Cole wrote:
> In fact, *all* the other *_COMMAND parameters to ExternalProject_Add
> yield a time-stamp managed "step" If the name of this parameter is
> EXTRACT_COMMAND, then I would strongly suggest conforming to the
> existing pattern, and making "extract" be
On 11/28/2013 08:58 AM, Samuel Martin wrote:
> When I try to link against it, "find_libray" correctly found it:
> ---
> CMakeCache.txt:
> FOO_LIBRARIES:INTERNAL=general;/usr/lib/foo.so
> ---
>
> But the generated linker flags are wrong:
> ---
> link.txt:
> /usr/bin/c++ -gCMakeFiles/bar.dir/m
2013/12/2 Nils Gladitz :
> On 12/02/2013 09:19 AM, Marcel Loose wrote:
>>
>> What would be the preferred way to pass the location of a built executable
>> target to ADD_TEST? By using the COMMAND option of ADD_TEST, or by using the
>> $ generator expression? Best regards, Marcel Loose.
>
> My perso
On 01/12/13 09:34, Nils Gladitz wrote:
> On 30.11.2013 20:49, Marcel Loose (Astron) wrote:
>> According to the CMake documentation, the TARGET property LOCATION for a
>> non-imported target is provided for compatibility with CMake 2.4 and
>> below. My question is: are there any plans to deprecate t
On 12/02/2013 09:19 AM, Marcel Loose wrote:
What would be the preferred way to pass the location of a built
executable target to ADD_TEST? By using the COMMAND option of
ADD_TEST, or by using the $ generator expression? Best
regards, Marcel Loose.
My personal preference would be the NAME/COMM
10 matches
Mail list logo
