The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14194
==
Reported By:Yichao Yu
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14195
==
Reported By:Yichao Yu
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14196
==
Reported By:Roman80
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14198
==
Reported By:Mark Stijnman
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14201
==
Reported By:Marcel Beister
Assigned To:
Stephen,
On 06/04/2013 10:49 AM, Mantis Bug Tracker wrote:
http://www.cmake.org/Bug/view.php?id=14201
==
Summary:FindCUDA does not forward include directories
assigned by target_include_directories()
Brad King wrote:
Stephen,
On 06/04/2013 10:49 AM, Mantis Bug Tracker wrote:
http://www.cmake.org/Bug/view.php?id=14201
==
Summary:FindCUDA does not forward include directories
assigned by
Hi,
I've pushed my current work to my clone in the INTERFACE_LINK_LIBRARIES-prop
topic. It's not yet complete, but I think it has almost all elements of the
solution.
Brad King wrote:
I wonder if we can distinguish PUBLIC/PRIVATE/INTERFACE for STATIC
for application of usage requirements.
Hi all,
I recently tweaked my Rogue7 dashboard's undefined behaviour checks and now
there are two test failures:
http://open.cdash.org/viewTest.php?onlyfailedbuildid=2926604
'ExternalProject' is a libarchive bug which I filed here:
http://code.google.com/p/libarchive/issues/detail?id=320
On 06/04/2013 01:30 PM, Sean McBride wrote:
'CTestTestFdSetSize' is superficially happening in an OS header's macro:
static __inline int
__darwin_fd_isset(int _n, const struct fd_set *_p)
{
return (_p-fds_bits[_n/__DARWIN_NFDBITS] (1(_n %
__DARWIN_NFDBITS)));
}
where right
What is this change qt4-macros-TARGET-arg?
Things get dicey when you want to pass things like include directories as
arguments. There are quotes to deal with as well as maximum argument
length issues. I'm not saying it can't be done, but it needs to be done
*carefully*.
I would really really
On 06/04/2013 02:01 PM, James Bigler wrote:
What is this change qt4-macros-TARGET-arg?
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ce60ff5
I would really really like generation time callbacks.
The $TARGET_PROPERTY:... expression is one, so you're in luck.
-Brad
--
Powered by
See the below forwarded message for details on an issue with testing symbols
that warrants discussion. Eike patched CheckSymbolExists last year which
changed it from primarily testing declaration to also enforcing linkage (and
introducing a ISO C problem in the process). Even if it fits the
On Tue, Jun 4, 2013 at 12:06 PM, Brad King brad.k...@kitware.com wrote:
On 06/04/2013 02:01 PM, James Bigler wrote:
What is this change qt4-macros-TARGET-arg?
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ce60ff5
OK, that looks similar to how I would have written it.
I would
See the below forwarded message for details on an issue with testing symbols
that warrants discussion. Eike patched CheckSymbolExists last year which
changed it from primarily testing declaration to also enforcing linkage (and
introducing a ISO C problem in the process). Even if it fits the
On 06/04/2013 03:46 PM, James Bigler wrote:
The $TARGET_PROPERTY:... expression is one, so you're in luck.
OK, so now I'm confused. I see a file(WRITE) that is a configure time
write, but the content of the file has generation time stuff in it like
On 06/04/2013 11:44 AM, Stephen Kelly wrote:
I've pushed my current work to my clone in the INTERFACE_LINK_LIBRARIES-prop
topic. It's not yet complete, but I think it has almost all elements of the
solution.
+CMake 2.8.11 consumed the 'link interface' of a target from properties
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14203
==
Reported By:André Caron
Assigned To:
Ah, yes. I see that now. I didn't read the code closely enough.
This gets closer to what I want in terms of generate time callbacks, but if
I need to process the output in some way then I'm still out of luck. For
FindCUDA I need to process C/CXX flags individually (i.e. run arbitrary
CMake
19 matches
Mail list logo