This is really a bug report to Nokia rather than a question. It seems that Carbide.c++ Express reorders include paths when you import an MMP file. For instance, having the following MMP file line:
SYSTEMINCLUDE path_a path_b path_c
And then importing this to Carbide.c++ Express and looking in the "includes" branch of the project tree might list the paths as:
Or in some other order.
The problem is that my project depends on include paths being in a certain order so I can't compile my project with Carbide.c++ Express. If the standard abld.bat build mechanism honours the ordering of the include paths in the MMP file then Carbide.c++ Express should as well.