[CMake] Cannot find source file:

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

Re: [CMake] Platform dSPACE

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

Re: [CMake] Platform dSPACE

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 compile

Re: [CMake] Platform dSPACE

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 CMAK

Re: [CMake] Platform dSPACE

> 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

Re: [CMake] Platform dSPACE

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 se

Re: [CMake] Platform dSPACE

> 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

Re: [CMake] Platform dSPACE

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), mo

Re: [CMake] Platform dSPACE

> 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 compil

Re: [CMake] Platform dSPACE

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 20

Re: [CMake] Platform dSPACE

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 com

[CMake] Platform dSPACE

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

[CMake] Questions about differences between building with Ninja and VS2017

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

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

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 y

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

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 I

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

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) fr

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 mi

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

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 pul

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

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

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

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