View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0013358CMakeCMakepublic2012-06-28 05:412012-10-24 17:24
Reportermuhkuh 
Assigned ToAlex Neundorf 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
Platformwin32OSWindowsOS Version7
Product VersionCMake 2.8.8 
Target VersionCMake 2.8.10Fixed in VersionCMake 2.8.10 
Summary0013358: Error importing generated Eclipse project with LIBRARY_OUTPUT_PATH set to ${CMAKE_CURRENT_BINARY_DIR}
DescriptionSetting LIBRARY_OUTPUT_PATH to the current binary directory in a CMakeLists.txt and using it with the "Eclipse CDT4 - MinGW Makefiles" generator creates an Eclipse project that causes an error when being imported into an eclipse workspace.

Steps To Reproduce1. Create CMakeLists.txt containing these two lines:
SET (LIBRARY_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR})
PROJECT ( Test )

2. Use the "Eclipse CDT4 - MinGW Makefiles" generator of cmake to create an Eclipse project. It doesn't matter if an in source or out of source build is done. For example CMakeLists.txt can reside in C:\TestProject\src and the Eclipse project is created at C:\TestProject\build.

3. Import this project into an eclipse workspace.
An error message appears:
"Error processing changed links in project description file."
"Cannot create a link to C:\TestProject\build because it overlaps the locations of the project that contains the linked resource."
Additional InformationAfter removing the line that sets LIBRARY_OUTPUT_PATH the generated project can be imported without errors.

Fortunately eclipse imports the generated project despite of the error message. It's just quite annoying.
TagsNo tags attached.
Attached Files

 Relationships

  Notes
(0030144)
Alex Neundorf (developer)
2012-07-28 07:57

 Interesting.
There is the function cmExtraEclipseCDT4Generator::AppendOutLinkedResource(), which handles those output directories.
If EXECUTABLE_OUTPUT_PATH is a subdir of CMAKE_BINARY_DIR, it does nothing.
In all other case, it seems Eclipse (at least Juno) complains that this is a bad location for a linked resource.
Maybe I should simply delete this code ?
I just tried with Eclipse Europa (3.3), and this old version also complains.
Has this ever worked ?
This is quite old code from 2007 or so.
(0030145)
Alex Neundorf (developer)
2012-07-28 12:44
edited on: 2012-08-02 15:59

 The note above was a bit too broad.
Can you give the branch EclipseFixBadLinkedResources on cmake stage a try ?
(0030168)
Alex Neundorf (developer)
2012-08-03 16:20

 I merged the branch into next, maybe it still makes it into 2.8.9, otherwise it will be 2.8.10.

 Issue History
Date Modified Username Field Change
2012-06-28 05:41 muhkuh New Issue
2012-07-27 16:33 Alex Neundorf Assigned To => Alex Neundorf
2012-07-27 16:33 Alex Neundorf Status new => assigned
2012-07-28 07:57 Alex Neundorf Note Added: 0030144
2012-07-28 12:44 Alex Neundorf Note Added: 0030145
2012-08-02 15:59 Alex Neundorf Note Edited: 0030145
2012-08-03 16:20 Alex Neundorf Note Added: 0030168
2012-08-03 16:20 Alex Neundorf Status assigned => closed
2012-08-03 16:20 Alex Neundorf Resolution open => fixed
2012-10-24 17:24 David Cole Fixed in Version => CMake 2.8.10
2012-10-24 17:24 David Cole Target Version => CMake 2.8.10

Copyright © 2000 - 2018 MantisBT Team