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.
Th
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, howev
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
lib
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 forgo
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 only
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 properties:
https://cmake.
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
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 ${DSPACE_TOOLS}/Compiler/
