Hi Daniel.
Your generator expression contains a space (between , and -I). Is it
quoted? Generator expressions are just normal strings until generate time,
and space normally separates CMake arguments. In other words, like this:
target_compile_options(trgt
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15518
==
Reported By:Paul TBBle Hampson
Assigned To:
With this change, does the external project's configure step re-run
when you edit only the CMAKE_CACHE_ARGS for it?
(It did with the *.in / configure_file approach...)
On Fri, Apr 17, 2015 at 12:55 AM, Andrey Pokrovskiy
wonder.m...@gmail.com wrote:
In current implementation of
HI,
Running OSX Snow Leopard, XCode 5.1.1
Command line tools installed.
If I type
clang --version
at the command line I get version 5.1
CMake 3.2.2
The first lines of outpuit I get are
The CXX compiler identification is AppleClang 5.1.0.5030040
The C compiler identification is AppleClang
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, maint has been updated
via 91d5261b58e97107fca610a868fbc283cbb8c856 (commit)
via
On 4/16/2015 6:15 PM, Domen Vrankar wrote:
I'm not certain that trying to squeeze the tests described above into
RunCMake is the right way to go.
[snip]
Would it be OK if I add something like CPackSemanticTests (I'm bad
with names) into Tests directory and implement it similarly to
RunCMake
On 4/17/2015 8:44 AM, Jon Hodgson wrote:
The CXX compiler identification is AppleClang 5.1.0.5030040
The C compiler identification is AppleClang 5.1.0.5030040
Good.
But then it bombs out at the line
PROJECT(${PROJECT_NAME} CXX C)
with the error
No CMAKE_CXX_COMPILER could be found
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 0da7fc85681d25e585b1a90f93af0ad23f9fdc82 (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, master has been updated
via 9efee16a7a092555d4bc40498a1acd957943a834 (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 4355acdb2da42cf59a7aa8a00e9d277caa95d27e (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, master has been updated
via 1f1b62b0e2598554349dce14542a4c383f620ada (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, master has been updated
via f4e5a0e6aa598f7cf0f34c2d7fea54e518615443 (commit)
via
Le 16/04/15 22:31, Brad King a écrit :
On 04/16/2015 04:19 PM, Domen Vrankar wrote:
I've pushed the patch with minor changes to next.
http://www.cmake.org/gitweb?p=cmake.git;h=0779b679
Thanks. The fixup! mark is useful only during incremental
development of an open topic. Once a commit is
On 17.04.2015 13:09, Sylvain Doremus wrote:
I have a strange output, related to the minimal CMakeLists.txt that I've
provided with this email.
My CMake version is 3.2.1, on Windows Seven SP1, the tested generators are
Visual Studio 10 2010 and Visual Studio 10 2010 Win64.
Here is the output
I have a strange output, related to the minimal CMakeLists.txt that I've
provided with this email.
My CMake version is 3.2.1, on Windows Seven SP1, the tested generators are
Visual Studio 10 2010 and Visual Studio 10 2010 Win64.
Here is the output I've got:
TestFolder/type
TestFolder
Eliminate your DOWNLOAD_COMMAND. CMake knows how to do it with just
the URL_MD5, DOWNLOAD_DIR and SOURCE_DIR information
HTH,
David
On Fri, Apr 17, 2015 at 1:32 AM, Cedric Doucet cedric.dou...@inria.fr wrote:
Hello David,
thank you very much for your help.
Unfortunately I may do
On 04/16/2015 05:54 AM, Tamás Kenéz wrote:
I think the main challenge will be how to format error messages when
neither mode finds anything for a REQUIRED package.
We can pretend they failed in the usual module;config order. So the
wordings of the messages may remain as they are.
The
Le 17/04/15 15:50, Raffi Enficiaud a écrit :
Le 16/04/15 22:31, Brad King a écrit :
On 04/16/2015 04:19 PM, Domen Vrankar wrote:
I've pushed the patch with minor changes to next.
http://www.cmake.org/gitweb?p=cmake.git;h=0779b679
Thanks. The fixup! mark is useful only during incremental
Hi Jon,
I can't really explain why, but I've seen the same problem on a colleague's Mac
as well. On my machine, it works just fine, but to get it working across all of
our Macs, I find I need to explicitly define the compilers by passing these
arguments to CMake on the command line:
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 bef4d783bf5694dc03cb6f1e1f5021df744f628e (commit)
via
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15519
==
Reported By:chenliang xu
Assigned To:
Hi,
I'm trying to use Cmake 3.2.2 to build with Cuda7 on Windows 8. I have
both Cuda 6.5 and Cuda 7.0 installed in these locations:
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v6.5
C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v7.0
When I try these:
find_package(CUDA 7.0 REQUIRED)
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 00b8efc2713bfd3e7ef56223bd6b0e9afcc9eaa0 (commit)
via
I'm working within a very large project on a python script. The script
gets passed through configure_file to replace some @VAR@ strings with some
file paths that are defined when cmake is run; this generates the final
script. The side effect is that whenever I modify the file and run make,
it
Well, if the file needs to have the substitutions performed, like after an
edit, CMake will have to run. What you could do is write a standalone cmake
script that just does the configure file step, then add it as a custom
command on a custom target, just running that configure script in script
With CUDA_SEPARABLE_COMPILATION enabled, I'm always getting linking
errors when I try to build. Seems it's looking for a directory that
doesn't exist:
'snip/build/CMakeFiles/SlicerLib.dir/Debug
If I manually create this directory, everything works. Seems that
either the directory path isn't
FindCUDA doesn't look for a specific version, but rather checks to see if
the version it found is the one you asked for. You can set the
CUDA_TOOLKIT_ROOT_DIR to the one you want (and reconfigure - I've set it up
to easily change this), or you can change your environment in Windows to
point to
Ah, thanks!
On Fri, Apr 17, 2015 at 3:36 PM, James Bigler jamesbig...@gmail.com wrote:
FindCUDA doesn't look for a specific version, but rather checks to see if
the version it found is the one you asked for. You can set the
CUDA_TOOLKIT_ROOT_DIR to the one you want (and reconfigure - I've set
20150417)
+set(CMake_VERSION_PATCH 20150418)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
Are you interested in working on a patch for this?
Yes, I'd give it a try. I signed up to Mantis, account: tamas.kenez so
you can assign it to me. I guess that's the next step.
Thanks,
Tamas
On Fri, Apr 17, 2015 at 2:01 PM, Brad King brad.k...@kitware.com wrote:
On 04/16/2015 05:54 AM, Tamás
30 matches
Mail list logo
