That's really not the best answer. I think what should happen is that you should use lib_c99.prefix instead of lib_ewl.prefix but right now I don't know how do that, nor am I 100% sure of other side effects.
I just discovered http://cache.freescale.com/files/soft_dev_tools/doc/ref_manual/EWL_C_Reference.pdf but right now I don't have time to read it....see page 163
of this document.
"The facilities in this header file are only available when the compiler is configured to
compile source code for C99 (ISO/IEC 9899:1999). Refer to the Build Tools Reference for
information on compiling C99 source code." (ed. Really? Why?)
My thoughts:
(a slow sigh*) I don't see the big deal over defining bool, true and false. For some reason, the "C" gods have made a deal out of this. If this is really the only issue, then you could advise that the user just do this - define bool true and false.
* to let out one's breath audibly, as from sorrow, weariness, or relief.
