Details
-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
Qt Creator 2.1.0
-
Symbian, Windows XP
-
1374f3b0d90358a5c710765cec60c04233fb4282
Description
I always wondered why Qt Creator is not able to find or parse includes like
#include <e32std.h>
Now, I logged the output of S60ToolChainMixin::epocHeaderPaths() and it seems that the EpocRoot is (in my case) an absolute path without drive letter. And that although the "S60 SDK" field of the Qt Version in the Options/Qt4 pane has actually a drive letter. The CppParser simply cannot resolve that path on Windows if Qt Creator is on another drive than the S60 SDK.
The only solution is imho that S60ToolChainMixin::epocHeaderPaths() returns full, absolute paths with drive letter. Just pick the drive letter from the "S60 SDK" field.