Build Environment for CW 10.1/MQX 7.2/52259EVB and HVAC demos

[jpa]

I can't build the HVAC demo for the 52259EVB, and it seems to be an environment/configuration problem.

The compiler says there's no prototype for strcmp.  There is an "include <string.h>" already, but if I explicitly add "#include <cstring>" the error goes away (and moves on to the next use of string.h).  

I installed CW 10.1 and MQX to the default directories.  I then imported the 10.1 project into CW, then imported the source files to the project directory.  In the project properties, I had to explicitly set MQX_ROOT_DIR to C:\Program Files\Freescale\Freescale MQX 3.7, since it was set to something like C:\ or C:\MQX by the original project.   At some point it seemed to be looking for a variable MCUToolsBaseDir that I couldn't find, so I tried putting such a definition, pointing to CW MCU v10.1\MCU, in Linked Resources.  When that didn't work, I tried putting MCUToolsBaseDirEnv in the environment.  

I've tried rebuilding the bsp_m52259evb and psp_m52259 projects, and got them to build with some tweaking, but it didn't help.  

Suggestions?

Edit: attached HVAC_Shell_Commands.args thinking it might help...

JPA

[jpa]

I think this could be considered a "bug" in the MQX demos...

Importing the project from the MQX demos directory causes the project properties to set the "User Recursive Path" to "${ProjDirPath}\..\.."  So if I'm interpreting this right, it's going to go two levels up from my current project directory and search everything below that for matches to any include files, including system files like <string.h>.  It was finding someone else's string.h file, so the compiler didn't complain about not finding the file.  So far, I've not seen a need for this path, after deleting it, the project builds without error.  

It does something similar to the Assembler path.  

(see C/C++ Build/Settings/Tool Settings->ColdFire Compiler->Input)

JPA