View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0015086

CMake

public

2014-08-14 06:22

2016-06-10 14:31

Reporter

Ignasi Rius

Assigned To

Kitware Robot

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

moved

Platform

Intel 32 or 64 bits

Windows

OS Version

8.1

Product Version

CMake 3.0.1

Target Version

Fixed in Version

Summary

0015086: CUDA_ADD_EXECUTABLE generates invalid VS2012 projects when source .cu file is a relative path beggining with "../"

Description

An invalid Visual Studio 2012 project is generated when CUDA_ADD_EXECUTABLE is called with a source file such as:

cuda_add_executable(testFindCuda ../3rdparty/testCuda.cu)

VS complaints that the .cu file is included in both the CustomBuild and None ItemGroups and the project simply doesn't load.

However, if the testCuda.cu file is specified with an absolut path everything works fine.

Steps To Reproduce

I have included a toy example to reproduce the problem (check testFindCuda.rar).

1) Just extract the files, and run cmake-gui (Windows) on testFindCuda/mainProject.
2) Generate a "Visual Studio 11 2012" solution.
3) Open the resulting .sln with VS2012 and you'll see that it's broken.

Additional Information

In particular it seems that the "offending line" in the .vcxproj file is:

<None Include="C:\Temp\testFindCuda\3rdparty\testCuda.cu" />

Tags

No tags attached.

Attached Files

testFindCuda.rar [^] (481 bytes) 2014-08-14 06:22

Relationships

Notes
(0042607) Kitware Robot (administrator) 2016-06-10 14:29	Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.

Issue History
Date Modified	Username	Field	Change
2014-08-14 06:22	Ignasi Rius	New Issue
2014-08-14 06:22	Ignasi Rius	File Added: testFindCuda.rar
2016-06-10 14:29	Kitware Robot	Note Added: 0042607
2016-06-10 14:29	Kitware Robot	Status	new => resolved
2016-06-10 14:29	Kitware Robot	Resolution	open => moved
2016-06-10 14:29	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed