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.
How to convert an Executable project type to a Static Library
Part Number: AM5728
Tool/software: Code Composer Studio
I have a TI test application that I'd now would like to use as the basis of a new static library. If I create a new static library project and start adding files and code from the original test exe project, I get a very large number of build errors. This means I would have to copy all the exe project settings to the static library settings bit by bit until all the errors are eliminated. This would be very tedious. It seems to me that if I made a copy of the exe project and changed it's name, and project type to static library I would have a much easier time. It would be easier to remove code and not have to change compiler and linker paths. But I saw on the forum that someone asked a similar question in 2012. The answer then was that changing project types would be too difficult. I'm wondering if things have changed in the last 6 years for CCS that might make changing a project type easier.
Kenneth Demers The answer then was that changing project types would be too difficult. I'm wondering if things have changed in the last 6 years for CCS that might make changing a project type easier.
It is still not possible to change the project type from executable to static library.
However, one thing you could do to make it easier to move over the settings is to copy the entire list of options from the existing project and paste them into the new project.
For example, you can get the list of compiler options from the location shown here. Copy them and then in the new project go to the same location and click the Edit Flags button and paste in the options.
Please click This Resolved My Issue if the reply answers your question.
Search the wikis for common questions: Compiler, CCSv6, CCSv7Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.