Community
Participate
Working Groups
The situation illustrated in the attachment still causes misunderstandings to users. In a managed C project sometimes appears an include folder. What cause its apperance is not clear. This could be still acceptable, what user do not undertand is why the include folder contains the following paths: ProjectName/Debug/C C:/Program the second path really has no meaning and is probably there because the window path "Program Files" contains a white space. It would be nice to have this situation clarified.
Created attachment 53359 [details] Managed C Project with include folder
What kind of project type/tool-chain are you using? Is this standatd "Gnu on Windows" project types supplied with CDT? Do you have any custom includes settings specified in your project, i.e. "C/C++ Build" property page -> "Tool Settings" -> "GCC C Compiler" -> "Directories" ? Mikhail
Hi Mikhail ! No, project properties are empty (default). What I've done is just: 1) created the new project 2) cheated the test.h file what we've got, that I could suppose a possible cause to the problem, are the following defined operating system environment variables: CPATH C:\Program Files\SYD-SDK\PThreads LIBRARY_PATH C:\Program Files\SYD-SDK\PThreads they are reflected in preferences for Managed Build - System Variables. Yes, we need both variables ! I'm not able to understand if both variables are the real problem, because the folder sometime appears and sometimes not.
Sorry, an answer was missing: To create the project I used the standard wizard contained in CDT. C->Managed Make C Project
Doug, would this be fixed now by your MinGW toolchain?
(In reply to comment #5) > Doug, would this be fixed now by your MinGW toolchain? Nope. It looks like a spaces in filename problem. The scanner discovery to set up the included calls gcc which probably returns these paths. This could be a problem with the scanner discovery output parser. Not sure...
