Bug 214029 - Changing mingw location does not remove old include entries from include path
Summary: Changing mingw location does not remove old include entries from include path
Status: RESOLVED DUPLICATE of bug 206372
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 4.0.1   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA Friend
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-30 19:15 EST by Willian Mitsuda CLA Friend
Modified: 2009-09-17 21:33 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Willian Mitsuda CLA Friend 2007-12-30 19:15:40 EST
I'm trying Wascana/CDT 4.0.1 and installed it in the default suggested location: C:\Program Files. It also installs mingw there.

I created a C project and it automatically detected the mingw location and added a include path there.

However, I had some problems to install an additional library to mingw (the scripts complained about the space in "Program Files" directory name), so I uninstalled it and reinstalled in c:\.

After opening my project again, it detected the new mingw directory, and added it correctly in the include path, but it didn't remove the old location.

So, I'm stuck with an extra include path entry pointing to old mingw location, and it stay giving me a warning at the problems view about "Invalid project path: Include path not found...".

Is there any workaround to clear this annoying message? I searched through all project files and didn't find any entry about this, so I suppose this is something managed/computed by the plugin, and not stored inside project files, right?
Comment 1 Axel Mueller CLA Friend 2008-05-05 02:59:09 EDT
Looks like a duplicate of bug #206372.
Comment 2 Andrew Gvozdev CLA Friend 2009-09-17 21:33:36 EDT
closing per prev comment

*** This bug has been marked as a duplicate of bug 206372 ***