Tool/software: Code Composer Studio
How to use CCS make .Lib document ?
If the .Lib document is called, the build result .hex document is different from that when .c and .h documents are directly called, is it right ?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Code Composer Studio
How to use CCS make .Lib document ?
If the .Lib document is called, the build result .hex document is different from that when .c and .h documents are directly called, is it right ?
Hi Ronnie,
Ronnie said:How to use CCS make .Lib document ?
To create and build a library (*.lib) project, the concept is the same as described in the link below:
The main difference is to expand the "Tool-chain" settings and select "Static Library" for the "Output type":
The rest of the process should be the similar in regards to adding source files, setting build options and building the project. The result of the build would be a library (*.lib) file.
Ronnie said:If the .Lib document is called, the build result .hex document is different from that when .c and .h documents are directly called, is it right ?
A .hex file is normally generated by taking the output of a build and using the hex converstion tool to generate a .hex file. See chapter 12 of the below document:
Thanks
ki