Stephane
S08, V1 (I presume a Coldfire) and Kinetis (plus STM32 maybe, or other Cortexes), multiple seat and as cheap as possible. This is quite a tough one:
- CW10 is certainly the best solution for the S08, V1 and Kinetis since it allows these to be used in a single environment (but it restricts to freescale and there is the possible size limitiation that could require mult-seat licenses to become necessary - although floating licenses woudl be a solution for work - maybe also for home if it is possible to solve the license part via Internet)
- Plus STM32, or other Cortex. This means that CW10 would not be suitable since it stops at freescale. Unfortunately good commerical products like IAR, Keil, Rowley etc. may be expensive since there is a version for each type (x3 license costs). Probably only IAR actually supports all families but the look and feel of each is at least the same. But, multi-seat and multi-processors may be available at discount prices if you ask.
- GCC - in such a case this may well be the way to go but the debugging part is usually the most critical - Eclipse allows editing and building but getting debugging working correctly for all targets may be the tricky bit - there are certainly various solutions in the form of plug-ins but actually getting them all to work may be the challenge (this is why there are various companies like Atollic and Mentor who put their packages together and sell them as an out-of-the-box solution, with support - it often proves cheaper to spend $1'000 (or $2'000) for a solution with support rather than paying an employee one months salary to get it working from the various open-source parts. But, if the number of seats gets high enough it can of course prove a reasonable investment.
Unfortunately also in this case such packages won't do S08, V1 and ARM - probably it still means three solutions to be purchased or invested in.
Also Eclipse is not absolutely necessary (unless you have certain plug-ins that benefit the project) since also taking VisualStudio special edition (possibly the best editor in the world?) is free. GCC can be build from a make file from it so editing and building is not a difficulty, but debugging is the key to real development efficiency, which it won't allow.
However there are still lots of projects which use serial interface based debugging (if the OS and project resouces are mature this can be adequate for verifying and debugging new code added to a project) meaning that the environment (Common editor and GCC build environment) can be deployed on all systems for all targets and serial output based debugging is at least available for all. This could be suitable when most people on the project will be doing occasional coding, building and programming. It would be possible to have maybe a small amount of seats for each processor targets from a good debug environment for main developers to solve more complicated issues. But this turns back full-circle to the floating license solution which essentially allows the IDE to be installed on every PC but just can't actually build on more that the license limit at any one time.
Something else to look at would be to consider a trace solution (look at iSYSTEM). This would move focus away from the classic IDE to the trace capabilities (unfortunately it may exclude S08 but is good for the others). It means investing in the debugger rather than the IDE since it allows any compiler to be used but supports loading, debugging and tracing - it is also built on VisualStudio. I think that it would be like everyone being able to program, build and compile (using GCC) [programming should be possible with simple and cheap debuggers for everyone] in a single environment but only the one with the interface at the time would actually be able to do the "quality-debugging". A bit like a floating debugging license in form of a dongle.
I think that you however have the basic problem faced by many companies with multiple targets and multiple development seats - the age old question of "make or buy". What is not so easy to identify at the beginning is which, make or buy, actually proves to be the cheapest at the end of the day. Sometimes make can turn out to be very expensive if it doesn't work out (putting together various cheap or free parts doesn't always result in something that is suitable for a team of professionals to do mission critial work with). Also, the manager responsible for the team may be putting his head and reputation on the line when something fails due to not having the correct tools for the job, and a project fails or its budget explodes due to the unforeseen complications that could have been avoided having the correct tools in place at the start. Many managers are not prepared to take such a risk and are happy to budget for good (if not necessarily cheap) tools. It also turns out that these managers and their projects are generally quite successful - I don't actually know many projects that have gone the other way (although there are the odd one or two, but not necessarily the most successful ones - with exceptions of course, as is always the case in life).
As I said, quite a tough one.
Regards
Mark