[Cmake-commits] CMake branch, master, updated. v3.9.1-456-ge4f16a0

_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170811) +set(CMake_VERSION_PATCH 20170812) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] FindIce module and C++11

On 11/08/17 20:15, Rolf Eike Beer wrote: Am Donnerstag, 10. August 2017, 10:28:31 schrieb rle...@codelibre.net: On 2017-08-10 09:50, Jones J.W. wrote: I'm building my code on Linux using the g++ flags "-std=c++11". This means that I must link with the libIce++11 libraries instead of libIce.

Re: [CMake] FindIce module and C++11

Am Donnerstag, 10. August 2017, 10:28:31 schrieb rle...@codelibre.net: > On 2017-08-10 09:50, Jones J.W. wrote: > > I'm building my code on Linux using the g++ flags "-std=c++11". This > > means that I must link with the libIce++11 libraries instead of > > libIce. > > > > The FindIce module,

Re: [CMake] FindIce module and C++11

On 2017-08-10 10:28, rle...@codelibre.net wrote: On 2017-08-10 09:50, Jones J.W. wrote: I'm building my code on Linux using the g++ flags "-std=c++11". This means that I must link with the libIce++11 libraries instead of libIce. The FindIce module, however as no provision for choosing these

Re: [CMake] Possible bug/incompatibility FindCUDA with Visual Studio 2017

Hi, Thanks for your pointers, problem solved. I have upgraded to CMake 3.9.1 (I don't think this matters though) and I switched to using the new CUDA CMake support as at your point 3). I am also using CUDA 9 RC which supports VS2017 (I was testing under CUDA 8 / CUDA 9 earlier, but just

Re: [cmake-developers] Developing Compiler files.

Hello. Yes, the bcc32 is provided by Borland and has Borland options and the bcc64 provided by Embarcadero and it is clang based and has Clang options but with old linker. The bcc32c is provided by Embarcadero and it is clang based but has Borland options wrapper. Actually I don't interested in

[Cmake-commits] CMake branch, master, updated. v3.9.1-455-gc47c011

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 c47c011c77bfd1bfb8d2060511a2b957ce181c62 (commit) via

[CMake] OBJECT Libraries and linking against targets

Hi, I understand vaguely why OBJECT libraries can't link against other targets, but I don't think the restriction in place needs to be so constrained. Consider the following: * A target is being create as an OBJECT library * A number of other targets are defined as INTERFACE target where they

[Cmake-commits] CMake branch, master, updated. v3.9.1-453-g73657a3

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 73657a35e6f64e530e8bbda90757c3762d7c36c6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.1-451-g1d51fca

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 1d51fcaeafeb9bfcdf3bc871d2b875446df081e8 (commit) via

Re: [CMake] Append to property COMPILE_DEFINITIONS

On 24 July 2017 at 04:32, Florian Lindner wrote: > > > [snip] > > Still, I don't undertand what is wrong with: > > set_property(GLOBAL APPEND PROPERTY COMPILE_DEFINITIONS > $<$:-FOO>) > > ? > What's wrong is that there is no such global property. See the list of global

Re: [cmake-developers] Developing Compiler files.

On 08/11/2017 03:18 AM, Валентин Хирный wrote: > I've tried to prepare cmake configuration file for Embarcadero bcc64 compiler. > For my practice I chose the name Embarcadero64 for new compiler because > bcc64 is clang based compiler. Does `bcc64` have a radically different command line interface

Re: [CMake] Referencing an OBJECT library

Hi Edward. "the reference to that OBJECT library is through $" - that is not quite true. When you're referring to the object library target itself (e.g. reading its properties), you use its name just like with any other target: get_property(someVar TARGET xxx PROPERTY TYPE) However, the genex

Re: [CMake] Platform dSPACE

I've got a follow-up question about cross-compiling for dSpace. My Toolchain file so far: set(CMAKE_SYSTEM_NAME dSpace) list(APPEND CMAKE_MODULE_PATH ${CMAKE_CURRENT_LIST_DIR}) file(TO_CMAKE_PATH "C:\\Program Files\\dSPACE RCPHIL 2016-B" DSPACE_TOOLS) set(DSPACE_PPCTOOLS

[cmake-developers] Developing Compiler files.

Hello. I've tried to prepare cmake configuration file for Embarcadero bcc64 compiler. For my practice I chose the name Embarcadero64 for new compiler because bcc64 is clang based compiler. I've prepared file fo determining compiler in the ...\CMake\share\cmake-3.9\Modules\Compiler folder (analog