Re: [CMake] Customizing component package file name
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 PACKAGE). Best to all! Piotr -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration?
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 messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Customizing component package file name
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 to:
${CPACK_RPM_PACKAGE_NAME}-${CPACK_RPM_PACKAGE_VERSION}-${CPACK_SYSTEM_NAME}-.rpm
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?
Thanks,
Piotr
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration?
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...@kitware.com] Sent: 21 June 2017 16:49 To: Hancox, James Cc: cmake@cmake.org; Robert Maynard Subject: Re: [CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration? 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 .vcxproj file by flag map entries here: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVS10CudaFlagTable.h#L3-6 Then a subset of the options that have dedicated elements defined by the CUDA VS integration are extracted by flag map entries here: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVS10CudaHostFlagTable.h Ideally we should then leave the rest in AdditionalCompilerOptions, but CUDA's VS integration puts them in the wrong place and breaks builds. Therefore we have to drop them: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVisualStudio10TargetGenerator.cxx#L2508-2510 We've reported this to NVIDIA but can't take the workaround out until a version of CUDA comes out that fixes it. -Brad __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration?
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 .vcxproj file by flag map entries here: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVS10CudaFlagTable.h#L3-6 Then a subset of the options that have dedicated elements defined by the CUDA VS integration are extracted by flag map entries here: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVS10CudaHostFlagTable.h Ideally we should then leave the rest in AdditionalCompilerOptions, but CUDA's VS integration puts them in the wrong place and breaks builds. Therefore we have to drop them: https://gitlab.kitware.com/cmake/cmake/blob/v3.9.0-rc3/Source/cmVisualStudio10TargetGenerator.cxx#L2508-2510 We've reported this to NVIDIA but can't take the workaround out until a version of CUDA comes out that fixes it. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Unable to build cmoka project using cmake
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 Staff R&D Engineer, Scientific Computing Kitware, Inc. On Wed, Jun 21, 2017 at 5:47 AM, Rajesh Kumar wrote: > 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. > > Regards > Rajesh > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration?
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 on the host compiler for a .cu file.
If I use the CUDA Visual Studio Integration GUI, I can do this through CUDA
C/C++->Host->Additional Compiler Options, which populates the
CudaCompile\AdditionalCompilerOptions section of the .vcxproj. At compile time
any flags in this field are passed to nvcc by the -Xcompiler flag, which in
turn passes them through to the host compiler.
Unfortunately I cannot find any way to achieve this through CMake. I have tried
to add it to CMAKE_CUDA_FLAGS like so:
set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -Xcompiler \"/bigobj\"")
But the generated .vcxproj does not have any trace of this line in it. (This
method does work for setting -Xcudafe parameters as expected, but it almost
seems like -Xcompiler flags are being deliberately stripped out.)
Is there some other mechanism for passing parameters into -Xcompiler?
Best wishes,
James Hancox
*To be precise, I'm using Visual Studio 12 2013 Win64 generator, CUDA 8.0.61
and CMake 3.9.0-rc3.
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] Unable to build cmoka project using cmake
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. Regards Rajesh -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] configuration dependency on include(...) files?
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_sources calls). When I touch / change a *.cmake file that is included (even directly) by the top-most CMakeLists file, it does not trigger the configuration step. I can certainly list every included *.cmake in the top-most CMAKE_CONFIGURE_DEPENDS property, but it seems to me that this step should not be necessary. Any advice or feedback is appreciated. Thanks, Tyrel -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
