daves Posted February 18, 2015 Share Posted February 18, 2015 We have seen a number of cases of build errors not making their way into the IDE. This leads to old binaries being downloaded and wasted hours/days of head scratching. I have managed to simply recreate one case which demonstrates the problem: New blank project Edit capp1.c #include #include "../../Include/pp_proj.h" #include "../../Include/error_utils.h" int main(void) { InitLibrary(); CloseLibrary(); return 0; } Create "error_utils.h" in Include folder: void DoFoo(void) { Foo = 1; // Error unknown variable } Build. All you see is a warning: ...C Language\Background Programs\capp1\capp1.c(4,0): Warning : in file included from capp1.c Build succeeded. This looks like another error parsing the compiler output or something. My guess is it has to do with the file having "error" in the name (if I rename to "errur_utils.h" it works). I have seen this in a number of situations so it may not be the only case... If you look at the err.log file: In file included from capp1.c:4: ../../Include/error_utils.h: In function 'DoFoo': ../../Include/error_utils.h:3: error: 'Foo' undeclared (first use in this function) ../../Include/error_utils.h:3: error: (Each undeclared identifier is reported only once ../../Include/error_utils.h:3: error: for each function it appears in.) make: *** [capp1.o] Error 1 How does this area work? Can you issue a fix? Link to comment Share on other sites More sharing options...
Recommended Posts