On 03/30/2015 12:49 AM, Geoffrey Viola wrote:
cmGlobalGhsMultiGenerator::FindMakeProgram uses the definition,
GHS_COMP_ROOT, to find gbuild.
Thanks. However, I don't think that approach will work. At the
point where GenerateBuildCommand is called in the case that is
failing, EnableLanguage
On 03/28/2015 09:34 PM, Michael Tanner wrote:
using the CMAKE_INCLUDE_SYSTEM_FLAG_C flag to treat NVIDIA's
include files as system headers.
Good idea.
- set(CUDA_NVCC_INCLUDE_ARGS ${CUDA_NVCC_INCLUDE_ARGS_USER}
-I${CUDA_INCLUDE_DIRS})
+ string(STRIP ${CMAKE_INCLUDE_SYSTEM_FLAG_C}
I know in the past setting all of NVidia's headers to be system includes
would actually break compilation of complex projects such as Thrust.
The reason for this was that in the past you would get the following error:
error: kernel launches from templates are not allowed in system files
On Mon,
On 03/29/2015 09:32 PM, Matt McCormick wrote:
That sounds cool. I have implemented it in the emulator-property branch [1].
The variable name that defines the default for the
CROSSCOMPILING_EMULATOR property is CMAKE_CROSSCOMPILING_EMULATOR.
Thanks. That looks pretty good, but needs some
On 21 Mar 2015, at 09:41, Stephen Kelly steve...@gmail.com wrote:
Anton Makeev wrote:
The other thing that seems troubling to me is that since file, target,
language compiler options are split into different parts of metadata, the
IDE need to know exactly how to assemble them back into
On 24 Mar 2015, at 00:54, Stephen Kelly steve...@gmail.com wrote:
Tobias Hunger wrote:
How about include_directories, compile_definitions and compile_flags?
So something along the lines of:
include_directories : [/foo, /opt]
compile_definitions : [DEF=\Foo\, OTHER_DEF=1]
On 30 Mar 2015, at 21:21, Alexander Neundorf neund...@kde.org wrote:
On Monday, March 30, 2015 19:04:10 Anton Makeev wrote:
On 24 Mar 2015, at 00:54, Stephen Kelly steve...@gmail.com wrote:
Tobias Hunger wrote:
How about include_directories, compile_definitions and compile_flags?
So
On Mon, Mar 30, 2015 at 7:04 PM, Anton Makeev
anton.mak...@jetbrains.com wrote:
Another item of note is that CMake does not know the compile flags as a
sequential container of individual flags currently, but it knows them as a
string (that's also why it appears as a string in my generated json
