I'm in the process of migrating a number of projects from an older XP/Eclipse/mspgcc environment to a CCS V6 based environment on Windows 10. The underlying toolchain is MSP430 GCC. In the old environment, builds were performed outside the IDE, but if possible I'd like to use the integrated builds in CCS.
There are a number of cases where the project produces nothing more than static objects, which are referenced by other projects as part of their builds (ie. no executables). The CCS model appears to be a single executable per project, and I'm trying to figure out the best way around this.
I've found a couple of references in the forums to static and dynamic library projects being an option in the project creation wizard, but has missed any sign of these in V6, or any other way of suppressing the linker phase of a project build? If I try and build the project, I get unresolved symbols on rts430.lib's call to main - setting the runtime support library to <none> is not enough, as CCS still tries to generate the .out. using an rts430. I've tried simply deleting the .out from the project specification, but this (not surprisingly) doesn't generate anything (and in particular, doesn't generate the objects). What is the magic to do this?
In a similar vein, some projects generate multiple executables. Many of these are simple test harnesses for the underlying components, but it does make a lot of sense to generate these within the appropriate project. The only way I've found to produce these is to have a separate project for each one. I'm guessing there has to be a better way.
I imagine both of these can be resolved by getting away from the automated make generation, but that gets me back to the old model we used, which is not ideal. I can't imagine what I'm attempting is unique, so I hope I'm missing something obvious!
Thanks for any pointers or help
Andrew