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.