Nokia Networks Home

Nokia nmake Product Builder

Quick Links

Related Products

Eclipse doesn't locate compile errors in the correct file

This problem has been observed with Eclipse 3.7 (Indigo), CDT 8.0, with the gcc compiler. When building with Eclipse CDT, sometimes compiler errors in the build console do not appear together with the other job action output but end up in some other part of the build log. When this happens Eclipse CDT cannot properly track the compilation directory in recursive builds and fails to locate the error in the correct C/C++ source file. This appears to be an output buffering issue. A workaround is to redirect stderr to synchronize it with stdout. For example, if the original CDT C/C++ build command (Project > Properties > C/C++ Build > Build Command) is set to something similar to:

nmake recurse_begin_message=gnu ProjDirPath=${ProjDirPath}

then the problem can be resolved by changing it to:

ksh -c 'nmake recurse_begin_message=gnu ProjDirPath=${ProjDirPath} 2>&1'

Alternatively a wrapper script can be used to call nmake with the redirection in the script.

Last Update: Friday,12-Aug-2016 10:45:08 EDT