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:
CPACK_RPM__FILE_NAME (without P
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 messa
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 equivalent
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 [mailto:brad.k...@kitwar
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 .vc
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 Atkins
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
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 suggest.
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 target_so
