Hi Adam, thank you very much for answering.
I tried to work with Visual Studio, running the makefile with the "build" button, as suggested in the forum. The big problem is that this way the IDE don't parse error messages comming from console.
An important role for me is that error messages appear clearly, discriminating what is "error" and what it is "warning", and the ability to click on the error message and take you directly to the line of code where the error occurred (cloud compiler has this feature, although it lacks "search" and "go to..." as well which is extremely slow to compile) I think for this to work, you must call gcc.exe from within IDE building configuration, instead that from the makefile.
Personally I feel the same, Visual Studio, Eclipse or Code::Blocks. I'm not a professional programmer, so I have worked with the 3 and I found them comfortable. Code::Blocks is perhaps the most appropriate regarding gcc and embedded programming.
Greetings.
P.S. sorry for my bad english, I'm from Uruguay.
I am working on updating the gcc4mbed project that Arthur Wolf and I have been working on and one of the work items on my list includes using an INCLUDE path that matches the cloud compiler. It appears to include almost every subdirectory in a project, including those of imported libraries but I was just wondering how inclusive it is and more importantly the exact search order.
I am hoping that someone happens to already know the particulars but I will resort to experimentation in an attempt to try and figure it out if I have to but that takes away from the time I could be using to shrink the C/C++ libraries and fixing known linker compatibility issues :)
Thanks for the help! I really appreciate it.