Hi Scott.
To file a bug, use the Mantis tracker at http://public.kitware.com/Bug/
As for running custom processing post-generation, there is no way hook
this, and a request for it was explicitly declined:
http://public.kitware.com/Bug/view.php?id=13020
Petr
On Mon, Jan 5, 2015 at 8:53 PM,
Hello,
On 05/01/15 20:09, Robert Goulet wrote:
My project needs to link with an external library which actually consist
of a set of libraries. Adding these libs using target_link_libraries
should be working just fine but unfortunately these libs have a bunch of
circular dependencies, so it
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 56054b1982748475a350239ae42d99af0554242a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 9b8ba31802a3e89b8aa1f34b3dfa7521d47c235a (commit)
via
Am Montag, 5. Januar 2015, 00:22:51 schrieb Mark Abraham:
On Sun, Jan 4, 2015 at 3:02 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Mark Abraham wrote:
Hi,
The FindCUDA.cmake module since v3.0 has had a bug because it assumes
that when cross compiling that CMAKE_SYSTEM_PROCESSOR will
Just wanted to send this again, as the problem still exists. While
working on the libdynd project (https://github.com/libdynd/libdynd),
we've discovered two CUDA CMake issues that we'd like to help resolve.
Who are the right people to speak with about these?
Irwin
Irwin Zaid wrote:
Hi all,
On Mon, Jan 5, 2015 at 1:57 PM, Irwin Zaid irwin.z...@physics.ox.ac.uk
wrote:
Hi James,
Thanks for the quick reply! As I mentioned, we've hit two issues. The
first is the project dependencies one, which I'll try and describe more a
bit below. I'm not a CMake expert, so please bear with me.
Alright, this is a lot of progress!
1) We are using Makefiles. I agree with you about the dependency graph,
so I'll try and sort that out. I'll let you know what the result is.
2) I just checked and, indeed, the *_intermediate_link.o file is not
being passed -fPIC. Is this our problem? What
2. It looks as though CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS is only
looking at the configuration specific flags. You can add the flag
specifically to all your configs (e.g. CMAKE_CXX_FLAGS_DEBUG) or you could
try adding these lines of code in your FindCUDA.cmake file somewhere
in
20150105)
+set(CMake_VERSION_PATCH 20150106)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
The only CMake build dependency changes when doing separable compilation
are found in CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS. Basically what this
does is create a new rule to build an intermediate link file. For
everything but some versions of MSVC generators it adds a custom command to
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via be2007b08096c2ca1323141d07811f8018151e24 (commit)
via
Hi,
My project needs to link with an external library which actually consist of a
set of libraries. Adding these libs using target_link_libraries should be
working just fine but unfortunately these libs have a bunch of circular
dependencies, so it fails. In the makefile, we link with these
If I have a file that depended on another file (say file.cpp includes a.h
which includes b.h), and then I rename b.h to c.h is CMake able to detect
that b.h no longer exists on disk and remove the dependency from the
makefiles?
Right now the makefile still has a dependency to b.h which it cannot
I have found a bug in SLN generation when the property USE_FOLDERS is set to
on.
The order of the folders, and vcprojects added to the folders is not sorted.
It is sorted correctly if USE_FOLDERS is not set.
I have two questions, first, what is the appropriate mechanism for filing a
bug? I
Hi, I am wondering now that 3.1 is out if using add_executable() without
sources and later using target_sources() is a new supported way of creating
targets? The docs don’t actually say the sources are optional and you can later
use target_sources().
We currently have several macros we reuse
Hi James,
Thanks for the quick reply! As I mentioned, we've hit two issues. The
first is the project dependencies one, which I'll try and describe more
a bit below. I'm not a CMake expert, so please bear with me.
The second is what I've put under 2).
The only CMake build dependency changes
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15336
==
Reported By:Scott Aron Bloom
Assigned To:
I believe what you want to do is bring the libraries in as imported targets
and set the target property IMPORTED_LINK_INTERFACE_MULTIPLICITY (
http://www.cmake.org/cmake/help/v3.0/prop_tgt/IMPORTED_LINK_INTERFACE_MULTIPLICITY.html
).
By default the value should be 2 which means that we will list
19 matches
Mail list logo
