Ian Collins wrote, On 31/03/07 23:25:
Flash Gordon wrote:
>Ian Collins wrote, On 31/03/07 21:35:
>>Flash Gordon wrote:
Where I used to work you had to do all testing (not just customer
acceptance testing, which was a small fraction of testing) on code built
with the correct compiler using the same compilation options.
That must have slowed you down significantly.
No, not at all. Even in the late 80s we had simulators fast enough that
they did not slow us down.
I was thinking of build times,
Only been a problem on one system, and I don't think a Coral 66 compiler
that was old and creaky when I first came across it is really relevant.
one of the biggest problems I have is
embedded tool chains not supporting parallel or distributed building,
Generally I've found you can use whatever "make" system you want. I've
used anything from simple scripts which just compile everything, to
complex scripts that write scripts to compile and link everything, so
make utilities to I can't remember what.
which can be a real pain for big projects. I like to keep build times
down to a minute or maybe two for a full build.
I generally find incremental builds more than sufficient except when
building for final test and release.
Also, for module level testing we generally built just that one module
and its test harness, not all of the rest of the SW. The development
systems in question did not do any cross-module (or whole program)
optimisation so this was valid.
--
Flash Gordon
