This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I have installed cygwin and “C/C++ development Pack”, on Windows XP, following these installation instructions: http://www.netbeans.org/community/releases/55/cnd-install.html However my setting in “Tools > Options > C/C++ > Code Assistance > Parser Settings” is not recognized. When I open welcome.cc file form Welcome sample project, I see an error on #include <iostream.h> specifying that “Cannot find include file”, whereas compilation and execution don’t produce any error. In parser setting, there is this line: /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/backward and I have checked: file iostream.h exists in “C:\Progs\cygwin\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\backward” directory. Workaround: I have duplicated (in same order) all directories in the setting, and all works.
I see that I have forgotten an important detail. I have duplicated all paths with windows path. For example: /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/backward Has been duplicated as: C:\Progs\cygwin\lib\gcc\i686-pc-cygwin\3.4.4\include\c++\backward
The category for C/C++ Pack is "cnd".
Sorry
Is this really a P3? Or should it maybe be a P2? It seems like this would affect everyone who uses the C/C++ Pack on WinXP, which might be rather a large percentage of the C/C++ Pack users, right? I know it bit me.... Admittedly, the work around is easy enough to use, but it certainly does not make for a very good first impression/out-of-box experience.
I agree, at least P2 to pay more attention on this usability bug. We have tools rework (http://www.netbeans.org/issues/show_bug.cgi?id=90786) which should simplify configuration and validatation of used settings.
Removing dependency on 90786. That task was never intended to rewrite the code assistance panel.
I believe this has been fixed (in 5.5.1). Paths in parser options dialog are now 'Windows' paths. Or am I missing something? Will mark this bug FIXED. Please reopen with explanation of what is not working if it still doesn't work with 5.5.1.
verified in build 200711011200