_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170621)
+set(CMake_VERSION_PATCH 20170622)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
2017-06-21 14:03 GMT-04:00 Piotr Sipika :
> Am I going about this the right way?
> Is setting CPACK_RPM__PACKAGE_FILE_NAME the right way to
> have a component-specific .rpm name?
Figured out what my problem was: I was using the incorrect variable
name, it should be:
On 06/21/2017 12:04 PM, Hancox, James wrote:
> Sadly it's a bit of a showstopper right now
I found a better workaround that can preserve -Xcompiler flags.
Please see the MR here:
https://gitlab.kitware.com/cmake/cmake/merge_requests/996
-Brad
--
Powered by www.kitware.com
Please keep
Hello all,
I'm trying to package a set of components, each in its own binary RPM.
I'm setting CPACK_RPM__PACKAGE_FILE_NAME to be something like:
${CPACK_RPM_PACKAGE_NAME}--${CPACK_RPM_PACKAGE_VERSION}-${CPACK_SYSTEM_NAME}
but the resulting CPACK_OUTPUT_FILE_NAME ends up being something
Hi Brad,
Thanks for the information, that makes a lot of sense. Here's hoping that CUDA
9 fixes the problem! Sadly it's a bit of a showstopper right now, but I'll be
sure to try this again in a future version.
Cheers,
James
-Original Message-
From: Brad King
On 06/21/2017 09:08 AM, Hancox, James wrote:
> it almost seems like -Xcompiler flags are being deliberately stripped out.)
Unfortunately we have to strip them out to work around a bug in CUDA's VS
integration.
The -Xcompiler options are parsed for inclusion in AdditionalCompilerOptions
in the
Hi Rajesh,
We would need more information to be useful:
- What version of CMake are you using?
- What compiler and version are you using?
- What OS and version are you using?
- Do you have separate source and build directories?
- How are you running cmake?
--
Chuck
Hi all,
I'm trying out the CMake 3.9.0-rc3 support for CUDA with Visual Studio
generators*, and trying to port over an existing project that uses FindCUDA.
I'm sure I'm missing something obvious, but I can't see any mechanism to set
-Xcompiler flags.
To be more explicit, I need to set /bigobj
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, release has been updated
via ab4c3270ae7062a8f3296055b9f6443b80f3aef2 (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 ad4a68cca00af3a20caaafbb96be67a1cc53a027 (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 d7c694b2e7ba43f634e920800efe138987d3b248 (commit)
via
Hi All,
I am unable to build cmocka project using Cmake. The below are the errors
which I'm facing.
"The C compiler identification is unknown"
"System is unknown to cmake, create: to use this system, please send your
config file to cm...@www.cmake.org so it can be added to cmake"
Please
Should the cmake configuration step automatically depend on other
included cmake files, i.e. via the include(...) command? We're using
"Unix Makefiles" under version 3.9.
In our project, we have a number of nested include(...) calls to list
source files at various levels (via lots of
13 matches
Mail list logo