TI's build process seems to be getting out of control. Why can't TI provide makefiles so we can use these as a baseline if the fancier tools do not work? The rts libraries are now (CCSv5) supposed to build themselves on first use! How is anyone meant to know what is going on?
My suggestion is please just supply a makefile.
When we try to load an executable into a CCS simulator that does not match there is an error message to that effect, which is good. But it would be better if there was a way to interrogate the binary to find what target it thinks it is built for, and what the logic is going on to determine whether or not it is acceptable for the target of the load.
My question is, does TI provide documentation for target type information that is somehow embedded in the binaries?
↧
Forum Post: questions about TI's build process
↧