[CMake] Cannot find source file:

[Sean Wayland]

Hi all,
I am having trouble getting an application to build.
I keep getting this error "cannot find source file"


/Users/seanwayland/Desktop/CATSMAT-masterfri/catsmat/catsmat/Analysis/src/*.cpp

This is the first folder containing sources and when it doesn't find
anything here it stops.

There are indeed .cpp files in that directory.
I tried putting a ./ at the start of the directory tree but it didn't help.

My cmake file is below .. I am using CLION 2017.1.1 and OSX 10.12.1

Can anyone shed any light ??

Thanks for your help!

Best Sean

###
# CMAKE CATSTMAT
###
cmake_minimum_required(VERSION 2.4)
set(CMAKE_CXX_STANDARD 11)
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release)
endif()

if(UNIX)
add_definitions(-Wall -DGCC)
endif(UNIX)

# RPATH SETTING #
set(CMAKE_MACOSX_RPATH 1)

#if(APPLE)
# set (CMAKE_OSX_ARCHITECTURES "x86_64 i386")
# if (${CMAKE_SYSTEM_VERSION} VERSION_LESS 9.0.0)
# set (CMAKE_OSX_SYSROOT /Developer/SDKs/MacOSX10.4u.sdk)
# elseif (${CMAKE_SYSTEM_VERSION} VERSION_LESS 10.8.0)
# set (CMAKE_OSX_SYSROOT /Developer/SDKs/MacOSX10.5.sdk)
# elseif (${XCODE_VERSION} VERSION_LESS 4.0.0)
# set (CMAKE_OSX_SYSROOT /Developer/SDKs/MacOSX10.6.sdk)
# else ()
# set (CMAKE_OSX_SYSROOT "macosx10.7")
# endif ()
# set (CMAKE_C++_FLAGS -mmacosx-version-min=10.4)
#endif(APPLE)
#
#if(WIN32)
# add_definitions(-DWINVER=0x0400 -DWIN32)
# if(${CMAKE_GENERATOR} STREQUAL "Visual Studio 6")
#  add_definitions(-DVC6)
# elseif(${CMAKE_GENERATOR} STREQUAL "Visual Studio 8 2005")
#  add_definitions(-DVC2005)
# endif(${CMAKE_GENERATOR} STREQUAL "Visual Studio 6")
#endif(WIN32)

###  BOOST LIBRARIES ###
if (APPLE)
set(BOOST_ROOT "/usr/local/boost")
set(BOOST_FILESYSTEM_LIB  /usr/local/boost/lib/libboost_filesystem.dylib)
set(BOOST_SYSTEM_LIB  /usr/local/boost/lib/libboost_system.dylib)

else ()
set(BOOST_ROOT "C:/local/boost_1_58_0")
set(BOOST_FILESYSTEM_LIB  C:/local/boost_1_58_0/lib64-msvc-12.0)
set(BOOST_SYSTEM_LIB  C:/local/boost_1_58_0/lib64-msvc-12.0)
endif ()

FIND_PACKAGE( Boost 1.58.0 REQUIRED  )
INCLUDE_DIRECTORIES( ${Boost_INCLUDE_DIR} )


###
# set directories, src and headers.

set (CATSMAT_DIR
./Users/seanwayland/Desktop/CATSMAT-masterfri/catsmat/catsmat/ )

set (libIMUSANT_DIR${CMAKE_CURRENT_SOURCE_DIR}/../../libIMUSANT)
set (LOKI_DIR   ${CMAKE_CURRENT_SOURCE_DIR}/../../Loki)
set (SUFFIX_TREE_DIR${CMAKE_CURRENT_SOURCE_DIR}/../../SuffixTree)
set (GOOGLE_TEST_INC_DIR
${CMAKE_CURRENT_SOURCE_DIR}/../../googletest-master/googletest/include)
set (IMUSANT_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../libIMUSANT)


set (LIBMUSICXML_DIR${CMAKE_CURRENT_SOURCE_DIR}/../../libMusicXMLv3)

set (SRCFOLDERS


${CATSMAT_DIR}/Analysis/src
${CATSMAT_DIR}/CounterpointAnalysis/src
${CATSMAT_DIR}/GeneralAnalysis/src
${CATSMAT_DIR}/Segmentation/FixedPeriodDetection/src
${CATSMAT_DIR}/Segmentation/LocalBoundaryDetectionModel/src
${CATSMAT_DIR}/Application
${CATSMAT_DIR}/Segmentation/LocalBoundaryDetectionModel/src
${CATSMAT_DIR}/Segmentation
${CATSMAT_DIR}/Utilities
)


set (INCFOLDERS
${libIMUSANT_DIR}
${CATSMAT_DIR}/Analysis/inc
${CATSMAT_DIR}/Application
${CATSMAT_DIR}/CounterpointAnalysis/inc
${CATSMAT_DIR}/GeneralAnalysis/inc
${CATSMAT_DIR}/Segmentation
${CATSMAT_DIR}/Segmentation/FixedPeriodDetection/inc
${CATSMAT_DIR}/Segmentation/LocalBoundaryDetectionModel/inc
${CATSMAT_DIR}/Utilities
${libIMUSANT_DIR}/DomainObjects/inc
${libIMUSANT_DIR}/Utilities/inc
${libIMUSANT_DIR}/FileProcessing/inc
${libIMUSANT_DIR}/Converters/MusicXML_v3
${libIMUSANT_DIR}/Converters/MusicXML_v3/inc
${libIMUSANT_DIR}/Converters/MusicXML_v3/shared/inc
${IMUSANT_DIR}/DomainObjects/inc
${IMUSANT_DIR}/Converters/MusicXML_v3
${IMUSANT_DIR}/Converters/MusicXML_v3/inc
${IMUSANT_DIR}/Converters/Shared/inc
${IMUSANT_DIR}/FileProcessing/inc
${IMUSANT_DIR}/Utilities/inc
${SUFFIXTREE_DIR}
${LIBMUSICXML_DIR}/libmusicxml-3.00-src/src
${LIBMUSICXML_DIR}/libmusicxml-3.00-src/src/lib
${LIBMUSICXML_DIR}/libmusicxml-3.00-src/src/visitors
${LIBMUSICXML_DIR}/libmusicxml-3.00-src/src/parser

${LOKI_DIR}
${SUFFIX_TREE_DIR}
${GOOGLE_TEST_INC_DIR}
)


foreach(folder ${SRCFOLDERS})
set(SRC ${SRC} "${folder}/*.cpp") # add source files
endforeach(folder)
file (GLOB CORESRC RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} ${SRC})





foreach(folder ${INCFOLDERS})
set(HEADERS ${HEADERS} "${folder}/*.h") # add header files
set(INCL ${INCL} "${folder}") # add include folders
endforeach(folder)
file (GLOB COREH RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} ${HEADERS})


###
# set includes
include_directories( ${INCL})
set_source_files_properties (${COREH} PROPERTIES HEADER_FILE_ONLY TRUE)


###
# set library targ

Re: [CMake] Platform dSPACE

[Robin Verschueren]

Dear Nils,

Perfect! This was exactly what I was looking for.
It works, and the CMAKE_INCLUDE_FLAG_C
is not overwritten.

Thanks,
Robin

On Fri, 23 Jun 2017 at 13:29 Nils Gladitz  wrote:

> On 23.06.2017 21:47, Robin Verschueren wrote:
>
> Dear CMake,
>
> We are trying to build our application for the dSPACE embedded system
> (www.dspace.com), more specifically their MicroAutobox-II. This makes
> use of a specific compiler called mccppc (Microtec C/C++ PowerPC compiler).
>
> I was following the instructions on this wiki page
> , when I got the following
> warning,
> when trying to use a custom 'Toolchain' file:
>
> System is unknown to cmake, create:
>
> Platform/dSPACE to use this system, please send your config file to
>
> cm...@www.cmake.org so it can be added to cmake
>
> We would be glad to send it to you when it is finished, but in the
> meantime,
> we cannot debug our toolchain file because of above warning.
>
> Is there a way of including it without having to include it in the
> official CMake
> distribution? I tried setting CMAKE_MODULE_PATH but that did not help..
>
>
> In the Toolchain file:
> set(CMAKE_SYSTEM_NAME dSPACE)
>
> list(APPEND CMAKE_MODULE_PATH ${CMAKE_CURRENT_LIST_DIR})
>
> ...
>
> Then having Platform/dSPACE.cmake next to your toolchain file should work
> (works for me).
>
>
> Nils
>
>
-- 

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] Platform dSPACE

[Nils Gladitz]

On 23.06.2017 21:47, Robin Verschueren wrote:

Dear CMake,

We are trying to build our application for the dSPACE embedded system
(www.dspace.com ), more specifically their 
MicroAutobox-II. This makes
use of a specific compiler called mccppc (Microtec C/C++ PowerPC 
compiler).


I was following the instructions on this wiki page 
, when I got the 
following warning,

when trying to use a custom 'Toolchain' file:

System is unknown to cmake, create:

Platform/dSPACE to use this system, please send your config file to

cm...@www.cmake.org  so it can be added to 
cmake



We would be glad to send it to you when it is finished, but in the 
meantime,

we cannot debug our toolchain file because of above warning.

Is there a way of including it without having to include it in the 
official CMake

distribution? I tried setting CMAKE_MODULE_PATH but that did not help..


In the Toolchain file:
set(CMAKE_SYSTEM_NAME dSPACE)

list(APPEND CMAKE_MODULE_PATH ${CMAKE_CURRENT_LIST_DIR})

...

Then having Platform/dSPACE.cmake next to your toolchain file should 
work (works for me).


Nils

-- 

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] Platform dSPACE

[Robin Verschueren]

Okay, that sounds reasonable. It's a pity, because that clutters the
CMakeLists of
potentially a lot of subfolders, e.g.:

if(EMBEDDED_SYSTEM1)
include(SYSTEM1_SPECIAL_FLAGS)
elseif(EMBEDDED_SYSTEM2)
include(
etc.

It would be nicer to just specify that from the command line:

cmake -D CMAKE_TOOLCHAIN_FILE= ..

Thanks for the help!
Robin

On Fri, 23 Jun 2017 at 13:17 Michael Ellery  wrote:

>
> > On Jun 23, 2017, at 1:11 PM, Robin Verschueren <
> robin.verschue...@gmail.com> wrote:
> >
> > Thank you, that makes sense.
> >
> > If I do that, how can I set specific settings for this Platform only? It
> seems that e.g.
> >
> > set(CMAKE_INCLUDE_FLAG_C "-J")
> >
> > in the Toolchain file is overwritten by CMake after processing the
> Toolchain file
> > (more specifically, in CMakeGenericSystem.cmake).
> >
> > Or should I set this variable somewhere else?
> >
> > Best,
> > Robin
>
> I think you use the toolchain file to declare the basics (what compiler to
> use) and then you can add specific flags and other settings in your other
> CMAKE files *after* the project() declaration (which usually clobbers a
> bunch of settings…). If you want to have your compiler flags/settings in a
> reusable file, you can just use the basic include() support to import a
> separate file, but it still needs to come after project() most likely.
>
>
>
>
-- 

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] Platform dSPACE

[Michael Ellery]

> On Jun 23, 2017, at 1:11 PM, Robin Verschueren  
> wrote:
> 
> Thank you, that makes sense.
> 
> If I do that, how can I set specific settings for this Platform only? It 
> seems that e.g.
> 
> set(CMAKE_INCLUDE_FLAG_C "-J")
> 
> in the Toolchain file is overwritten by CMake after processing the Toolchain 
> file
> (more specifically, in CMakeGenericSystem.cmake).
> 
> Or should I set this variable somewhere else?
> 
> Best,
> Robin

I think you use the toolchain file to declare the basics (what compiler to use) 
and then you can add specific flags and other settings in your other CMAKE 
files *after* the project() declaration (which usually clobbers a bunch of 
settings…). If you want to have your compiler flags/settings in a reusable 
file, you can just use the basic include() support to import a separate file, 
but it still needs to come after project() most likely.



-- 

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] Platform dSPACE

[Robin Verschueren]

Thank you, that makes sense.

If I do that, how can I set specific settings for this Platform only? It
seems that e.g.

set(CMAKE_INCLUDE_FLAG_C "-J")

in the Toolchain file is overwritten by CMake after processing the
Toolchain file
(more specifically, in CMakeGenericSystem.cmake).

Or should I set this variable somewhere else?

Best,
Robin


On Fri, 23 Jun 2017 at 13:03 Michael Ellery  wrote:

>
> > On Jun 23, 2017, at 1:01 PM, Michael Ellery 
> wrote:
> >
> >
> >> On Jun 23, 2017, at 12:47 PM, Robin Verschueren <
> robin.verschue...@gmail.com> wrote:
> >>
> >> Dear CMake,
> >>
> >> We are trying to build our application for the dSPACE embedded system
> >> (www.dspace.com), more specifically their MicroAutobox-II. This makes
> >> use of a specific compiler called mccppc (Microtec C/C++ PowerPC
> compiler).
> >>
> >> I was following the instructions on this wiki page, when I got the
> following warning,
> >> when trying to use a custom 'Toolchain' file:
> >>
> >> System is unknown to cmake, create:
> >> Platform/dSPACE to use this system, please send your config file to
> >> cm...@www.cmake.org so it can be added to cmake
> >>
> >> We would be glad to send it to you when it is finished, but in the
> meantime,
> >> we cannot debug our toolchain file because of above warning.
> >>
> >> Is there a way of including it without having to include it in the
> official CMake
> >> distribution? I tried setting CMAKE_MODULE_PATH but that did not help..
> >>
> >>
> >> Best regards,
> >> Robin
> >> --
> >
> > what happens if you set
> -DCMAKE_TOOLCHAIN_FILE=path/to/your/toolchain.cmake  when running
> cmake…does that give any different result?
> >
>
> sorry - I misunderstood the nature of your error. I think this might be
> relevant:
>
> "If your target is an embedded system without OS set CMAKE_SYSTEM_NAME
> to "Generic”.   “
>
>
>
-- 

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] Platform dSPACE

[Michael Ellery]

> On Jun 23, 2017, at 1:01 PM, Michael Ellery  wrote:
> 
> 
>> On Jun 23, 2017, at 12:47 PM, Robin Verschueren 
>>  wrote:
>> 
>> Dear CMake,
>> 
>> We are trying to build our application for the dSPACE embedded system
>> (www.dspace.com), more specifically their MicroAutobox-II. This makes
>> use of a specific compiler called mccppc (Microtec C/C++ PowerPC compiler).
>> 
>> I was following the instructions on this wiki page, when I got the following 
>> warning, 
>> when trying to use a custom 'Toolchain' file:
>> 
>> System is unknown to cmake, create:
>> Platform/dSPACE to use this system, please send your config file to 
>> cm...@www.cmake.org so it can be added to cmake
>> 
>> We would be glad to send it to you when it is finished, but in the meantime,
>> we cannot debug our toolchain file because of above warning.
>> 
>> Is there a way of including it without having to include it in the official 
>> CMake
>> distribution? I tried setting CMAKE_MODULE_PATH but that did not help..
>> 
>> 
>> Best regards,
>> Robin
>> -- 
> 
> what happens if you set
> -DCMAKE_TOOLCHAIN_FILE=path/to/your/toolchain.cmake  when running cmake…does 
> that give any different result? 
> 

sorry - I misunderstood the nature of your error. I think this might be 
relevant:

"If your target is an embedded system without OS set CMAKE_SYSTEM_NAME to 
"Generic”.   “


-- 

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] Platform dSPACE

[Robin Verschueren]

That's exactly what I did :)

On Fri, 23 Jun 2017 at 13:01 Michael Ellery  wrote:

>
> > On Jun 23, 2017, at 12:47 PM, Robin Verschueren <
> robin.verschue...@gmail.com> wrote:
> >
> > Dear CMake,
> >
> > We are trying to build our application for the dSPACE embedded system
> > (www.dspace.com), more specifically their MicroAutobox-II. This makes
> > use of a specific compiler called mccppc (Microtec C/C++ PowerPC
> compiler).
> >
> > I was following the instructions on this wiki page, when I got the
> following warning,
> > when trying to use a custom 'Toolchain' file:
> >
> > System is unknown to cmake, create:
> > Platform/dSPACE to use this system, please send your config file to
> > cm...@www.cmake.org so it can be added to cmake
> >
> > We would be glad to send it to you when it is finished, but in the
> meantime,
> > we cannot debug our toolchain file because of above warning.
> >
> > Is there a way of including it without having to include it in the
> official CMake
> > distribution? I tried setting CMAKE_MODULE_PATH but that did not help..
> >
> >
> > Best regards,
> > Robin
> > --
>
> what happens if you set
> -DCMAKE_TOOLCHAIN_FILE=path/to/your/toolchain.cmake  when running
> cmake…does that give any different result?
>
>
-- 

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] Platform dSPACE

[Michael Ellery]

> On Jun 23, 2017, at 12:47 PM, Robin Verschueren  
> wrote:
> 
> Dear CMake,
> 
> We are trying to build our application for the dSPACE embedded system
> (www.dspace.com), more specifically their MicroAutobox-II. This makes
> use of a specific compiler called mccppc (Microtec C/C++ PowerPC compiler).
> 
> I was following the instructions on this wiki page, when I got the following 
> warning, 
> when trying to use a custom 'Toolchain' file:
> 
> System is unknown to cmake, create:
> Platform/dSPACE to use this system, please send your config file to 
> cm...@www.cmake.org so it can be added to cmake
> 
> We would be glad to send it to you when it is finished, but in the meantime,
> we cannot debug our toolchain file because of above warning.
> 
> Is there a way of including it without having to include it in the official 
> CMake
> distribution? I tried setting CMAKE_MODULE_PATH but that did not help..
> 
> 
> Best regards,
> Robin
> -- 

what happens if you set-DCMAKE_TOOLCHAIN_FILE=path/to/your/toolchain.cmake  
when running cmake…does that give any different result? 

-- 

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] Platform dSPACE

[Robin Verschueren]

Dear Martin,

That's exactly what I'm doing. The trouble is that I want to use

set(CMAKE_SYSTEM_NAME dSPACE)

or something similar. But then I get this warning that `dSPACE.cmake'
is not found in the `Platform' folder. My question was how to circumvent
this.

Best regards,
Robin

On Fri, 23 Jun 2017 at 12:56 Martin Weber  wrote:

> Am Freitag, 23. Juni 2017, 19:47:32 CEST schrieb Robin Verschueren:
> > Dear CMake,
> >
> > We are trying to build our application for the dSPACE embedded system
> > (www.dspace.com), more specifically their MicroAutobox-II. This makes
> > use of a specific compiler called mccppc (Microtec C/C++ PowerPC
> compiler).
> >
> > I was following the instructions on this wiki page
> > , when I got the following
> > warning,
> > when trying to use a custom 'Toolchain' file:
>
> Sounds like you will have to create a custom toolchain file.
> Maybe this will help:
> 
>
> Martin
> --
> Cd wrttn wtht vwls s mch trsr.
>
>
> --
>
> 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

Re: [CMake] Platform dSPACE

[Martin Weber]

Am Freitag, 23. Juni 2017, 19:47:32 CEST schrieb Robin Verschueren:
> Dear CMake,
> 
> We are trying to build our application for the dSPACE embedded system
> (www.dspace.com), more specifically their MicroAutobox-II. This makes
> use of a specific compiler called mccppc (Microtec C/C++ PowerPC compiler).
> 
> I was following the instructions on this wiki page
> , when I got the following
> warning,
> when trying to use a custom 'Toolchain' file:

Sounds like you will have to create a custom toolchain file.
Maybe this will help:


Martin
-- 
Cd wrttn wtht vwls s mch trsr.


-- 

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] Platform dSPACE

[Robin Verschueren]

Dear CMake,

We are trying to build our application for the dSPACE embedded system
(www.dspace.com), more specifically their MicroAutobox-II. This makes
use of a specific compiler called mccppc (Microtec C/C++ PowerPC compiler).

I was following the instructions on this wiki page
, when I got the following
warning,
when trying to use a custom 'Toolchain' file:

System is unknown to cmake, create:

Platform/dSPACE to use this system, please send your config file to

cm...@www.cmake.org so it can be added to cmake

We would be glad to send it to you when it is finished, but in the meantime,
we cannot debug our toolchain file because of above warning.

Is there a way of including it without having to include it in the official
CMake
distribution? I tried setting CMAKE_MODULE_PATH but that did not help..


Best regards,
Robin
-- 

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] Questions about differences between building with Ninja and VS2017

[ken poole]

In our environment we have:
CMake 3.8.1
VS Enterprise 2017 15.1 (26403.7)
Ninja 1.7.2

Since we are building on Win Server 2012R2 and targeting Win7 we do define
the MS macros (_WIN32_WINNT, WINVER, _WIN32_WINDOWS, NTDDI_VERSION) to
ensure we only get access to the features that Win7 has.

When we look at the "MS include directories" in Visual Studio it shows as
referencing the Windows Kits\8.1 include directories
When we run with Ninja, we run in a cmd window that is titled "x64 Native
Tools Command Prompt for VS 2017" - and the includes in its environment
variables are the Windows Kits\10.0 ones.

Is there a way to have CMake generate for Ninja so it uses the same
"Windows Kits" directory as MSVS does? We have tried setting
CMAKE_SYSTEM_VERSION to 6.1. That doesn't seem to have made a difference.
What is that supposed to change in a Ninja/MSVS  build?

Are there some other settings we should be making to ensure the Ninja and
the MSVS builds work from the same directories?

Thanks,
-Ken P.
-- 

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] Visual Studio with CUDA does not work in 3.9

[Robert Maynard]

Hi

Unfortunately you are going to need to provide more information to
help track down the issue. We currently have machines that verify
2015/8.0 and 2013/7.5 properly work (
https://open.cdash.org/index.php?project=CMake&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=CUDA
)

Can you please provide run from the build directory cmake
--system-information  and send the results?

On Fri, Jun 23, 2017 at 9:11 AM, Mueller-Roemer, Johannes Sebastian
 wrote:
> Hi Robert,
>
> yes, according to the Windows installed program list, I have "NVIDIA CUDA 
> Visual Studio Integration 8.0" installed. I can also create CUDA projects via 
> "New project" and have an Nsight menu entry.
>
> Regards
> Johannes Mueller-Roemer
>
> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
> Tel +49 6151 155-606  |  Fax +49 6151 155-139
> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>
>
> -Original Message-
> From: Robert Maynard [mailto:robert.mayn...@kitware.com]
> Sent: Friday, June 23, 2017 14:52
> To: Mueller-Roemer, Johannes Sebastian 
> 
> Cc: CMake MailingList 
> Subject: Re: [CMake] Visual Studio with CUDA does not work in 3.9
>
> Hi,
>
> Do you have the NVIDIA CUDA Visual Studio Integration tools installed?
> This is needed for support when using the Visual Studio Generator(s).
> Otherwise you can still use ninja or the nmake generators.
>
> On Fri, Jun 23, 2017 at 7:06 AM, Mueller-Roemer, Johannes Sebastian 
>  wrote:
>> The absolute minimum example
>>
>>
>>
>> cmake_minimum_required(VERSION 3.9 FATAL_ERROR)
>>
>> project(cuda-test LANGUAGES C CXX CUDA)
>>
>> add_executable(cuda-test main.cu)
>>
>>
>>
>> Fails to configure with the error:
>>
>> CMake Error at CMakeLists.txt:2 (project):
>>
>>   No CMAKE_CUDA_COMPILER could be found.
>>
>>
>>
>> Am I missing something, or is the support mentioned in the change list
>> simply not true?
>>
>>
>>
>> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
>>
>> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
>>
>> Tel +49 6151 155-606  |  Fax +49 6151 155-139
>>
>> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>>
>>
>>
>>
>> --
>>
>> 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

Re: [CMake] Visual Studio with CUDA does not work in 3.9

[Mueller-Roemer, Johannes Sebastian]

Hi Robert,

yes, according to the Windows installed program list, I have "NVIDIA CUDA 
Visual Studio Integration 8.0" installed. I can also create CUDA projects via 
"New project" and have an Nsight menu entry.

Regards
Johannes Mueller-Roemer

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
Tel +49 6151 155-606  |  Fax +49 6151 155-139
johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de


-Original Message-
From: Robert Maynard [mailto:robert.mayn...@kitware.com] 
Sent: Friday, June 23, 2017 14:52
To: Mueller-Roemer, Johannes Sebastian 

Cc: CMake MailingList 
Subject: Re: [CMake] Visual Studio with CUDA does not work in 3.9

Hi,

Do you have the NVIDIA CUDA Visual Studio Integration tools installed?
This is needed for support when using the Visual Studio Generator(s).
Otherwise you can still use ninja or the nmake generators.

On Fri, Jun 23, 2017 at 7:06 AM, Mueller-Roemer, Johannes Sebastian 
 wrote:
> The absolute minimum example
>
>
>
> cmake_minimum_required(VERSION 3.9 FATAL_ERROR)
>
> project(cuda-test LANGUAGES C CXX CUDA)
>
> add_executable(cuda-test main.cu)
>
>
>
> Fails to configure with the error:
>
> CMake Error at CMakeLists.txt:2 (project):
>
>   No CMAKE_CUDA_COMPILER could be found.
>
>
>
> Am I missing something, or is the support mentioned in the change list 
> simply not true?
>
>
>
> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
>
> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
>
> Tel +49 6151 155-606  |  Fax +49 6151 155-139
>
> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>
>
>
>
> --
>
> 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

Re: [CMake] FILE(LOCK ... GUARD FILE) fails with cmake -P

[Robert Maynard]

Hi,

I have opened an issue reporting this problem:
https://gitlab.kitware.com/cmake/cmake/issues/17009

On Fri, Jun 23, 2017 at 2:23 AM, Sergey Zakharchenko
 wrote:
> Hello,
>
> CMake crashes on an assertion when I use FILE(LOCK ... GUARD FILE)
> inside of a file called (directly or indirectly) from cmake -P.
>
> $ cat x.cmake
> FILE(LOCK . DIRECTORY GUARD FILE)
>
> $ cat y.cmake
> INCLUDE(x.cmake)
>
> $ cmake -P  x.cmake
> Assertion failed: (!this->FileScopes.empty()), function LockFileScope,
> file 
> /wrkdirs/usr/ports/devel/cmake/work/cmake-3.5.0/Source/cmFileLockPool.cxx,
> line 76.
> Abort trap (core dumped)
>
> $ cmake -P y.cmake
> Assertion failed: (!this->FileScopes.empty()), function LockFileScope,
> file 
> /wrkdirs/usr/ports/devel/cmake/work/cmake-3.5.0/Source/cmFileLockPool.cxx,
> line 76.
> Abort trap (core dumped)
>
> I've tested this with different base systems and CMake versions from
> 3.4.1 to 3.7.2 with similar results (doesn't matter if I lock a file
> instead either). It's easy to work around (wrap code with function)
> but a bit inelegant. I understand there may be some limitation but
> there could at least be some sensible error message like with 'GUARD
> FUNCTION' when it's not used in a function definition...
>
> Best regards,
>
> --
> DoubleF
> --
>
> 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

Re: [CMake] Visual Studio with CUDA does not work in 3.9

[Robert Maynard]

Hi,

Do you have the NVIDIA CUDA Visual Studio Integration tools installed?
This is needed for support when using the Visual Studio Generator(s).
Otherwise you can still use ninja or the nmake generators.

On Fri, Jun 23, 2017 at 7:06 AM, Mueller-Roemer, Johannes Sebastian
 wrote:
> The absolute minimum example
>
>
>
> cmake_minimum_required(VERSION 3.9 FATAL_ERROR)
>
> project(cuda-test LANGUAGES C CXX CUDA)
>
> add_executable(cuda-test main.cu)
>
>
>
> Fails to configure with the error:
>
> CMake Error at CMakeLists.txt:2 (project):
>
>   No CMAKE_CUDA_COMPILER could be found.
>
>
>
> Am I missing something, or is the support mentioned in the change list
> simply not true?
>
>
>
> Fraunhofer-Institut für Graphische Datenverarbeitung IGD
>
> Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
>
> Tel +49 6151 155-606  |  Fax +49 6151 155-139
>
> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>
>
>
>
> --
>
> 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

Re: [CMake] Problem with fixup bundle and duplicate change commands on macOS

[Luis Caro Campos]

Hi Lukas,

Could you provide some details? Please do correct me if any of my
assumptions are wrong.

You are calling FIXUP_BUNDLE on an executable created this way:
add_executable(MyAppName MACOSX_BUNDLE ...),

and you need are calling FIXUP_BUNDLE so that the 3rd party library
dependencies are pulled into the bundle, so that the bundle becomes
standalone.

Is FIXUP_BUNDLE being called at build time ("make"), perhaps as custom
command that depends on the application target, or install time ("make
install"), as part of the INSTALL(...) directive in a cmake script?

What exactly do you mean by "duplicate commands" ?

In order to make the bundle standalone, I believe FIXUP_BUNDLE iteratively
goes through the dependencies of the main executable, which are 'hardcoded'
in the executable. You can list the depencies using
$ otool -L executableName

For each dependency (dylib shared library or a Framework), the dependencies
will be copied to the Frameworks folder in the bundle, based on their
install name, and the executable will be fixed using install_name_tool to
make sure that non-system libraries are loaded from the Frameworks folder.
If these dependencies have other dependencies, install_name_tool is also
called on them.

Sometimes there are hiccups, and unfortunately in some cases it may be
difficult to produce a truly re-locatable bundle if the install names of
some libraries are not fully "correct".

Regards,
Luis


On Thu, Jun 22, 2017 at 6:01 PM, Schulte, Lukas  wrote:

> Hey guys,
>
>
>
> So I’m trying to use fixup_bundle for our software, and for a reason that
> I can’t wrap my head around executing fixup_bundle results in a call to
> install_name_tool where in the changes variable some commands are
> duplicate (in my case, double deletion of an rpath during fixing up of
> some Qt dependencies, namely QtWebViewEngineCore).
>
> I didn’t find anyone with the same problem as me on the internet so I
> figured I would just ask you guys for advice.
>
>
> I’m using CMake 3.3.2 , Qt 5.9 and OsX 10.11.6.
>
> So my question is – what would be my best way of action here? As this is
> happening with automatically resolved dependencies, I don’t have much
> option to handle this in my own CMake files.
>
>
>
> What I could think of if there’s not something im doing horribly wrong
> was implementing a duplicate removal in BundleUtitilties.cmake which I
> would then discuss on the Developer List I guess- does anyone happen to
> have any better ideas or hints what I could do to solve this?
>
>
>
>
> Thanks in advance!
>
>
>
> Lukas
>
> 
> --
>
>
>
> Lukas Schulte
>
> PhD Student
>
> Max-Planck-Institute for biophysical Chemistry
>
> Department of Structural Dynamics
>
> Am Fassberg 11
>
> D-37077 Goettingen
>
> +49-551-201-1410 <+49%20551%202011410>
>
>
>
> --
>
> 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

Re: [CMake] No mechanism to set -Xcompiler options with Visual Studio CUDA integration?

[Hancox, James]

Hi Brad,

I picked up rc4 (since according to the release notes it has your changes 
merged in) and tried it out. Sadly I'm still running into problems! It looks 
like a semicolon is incorrectly added when -Xcompiler is appended to 
AdditionalOptions:

-lineinfo;-Xcompiler="/bigobj -Zi -Ob1"

This causes MSBuild to fail with the following error message:

1>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\BuildCustomizations\CUDA 
8.0.targets(635,9): error MSB5016: The name "-Xcompiler" contains an invalid 
character "-".  C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\BuildCustomizations\CUDA 8.0.targets

I tried manually replacing the semicolon with a space, and this fixes the issue 
for me (and -Xcompiler is passed through as expected). 

I've created a minimal test case to reproduce the error, and put it on Github 
at https://github.com/jameshancox/cmake_example_xcompiler , hope it helps.

Cheers,
James


-Original Message-
From: Brad King [mailto:brad.k...@kitware.com] 
Sent: 22 June 2017 15:06
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/22/2017 07:32 AM, Hancox, James wrote:
> That's great news! I'll definitely try that out in the next RC.

It should be in a nightly binary from here:

 https://cmake.org/files/dev/?C=M;O=D

The cmake-3.9.20170621-g87dac-win64-x64.zip file should have it and can be 
extracted and used without installing.

-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

[CMake] Visual Studio with CUDA does not work in 3.9

[Mueller-Roemer, Johannes Sebastian]

The absolute minimum example

cmake_minimum_required(VERSION 3.9 FATAL_ERROR)
project(cuda-test LANGUAGES C CXX CUDA)
add_executable(cuda-test main.cu)

Fails to configure with the error:
CMake Error at CMakeLists.txt:2 (project):
  No CMAKE_CUDA_COMPILER could be found.

Am I missing something, or is the support mentioned in the change list simply 
not true?

Fraunhofer-Institut für Graphische Datenverarbeitung IGD
Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany
Tel +49 6151 155-606  |  Fax +49 6151 155-139
johannes.mueller-roe...@igd.fraunhofer.de
 | www.igd.fraunhofer.de

-- 

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