There has been no other objection to removing BCC and Amitha's concern
was simply the long-term presence of those compiler errors. We should
give people more time to respond, but it seems to me that a good
comprimise is to turn off contrib for the BCC build. However, the BCC
errors exposed in contrib seem to indicate a problem with core/vnl.
Amitha and I looked at this briefly. Our only conclusion is that
enabling MSVC6 "workaround" documented in vnl_matrix_fixed.h does not
fix this BCC problem (a quick long-shot at a fix).
From: Brad King [mailto:brad.king@...
Sent: Wednesday, June 27, 2007 10:16 AM
To: Amitha Perera; vxl-maintainers@...;
Subject: Re: [Vxl-maintainers] VXL dashboard
Amitha Perera wrote:
> I suggest that we remove bcc 5.5 from the dashboard, because it's such
> an old compiler.
ITK still uses this compiler and has a dashboard for it. Since I have
to support upstream vxl with ITK I'd like to keep this compiler on the
vxl dashboard. However ITK only uses vnl, vnl_algo, and its
dependencies (vcl, netlib). It looks like the recent errors for bcc55
on the vxl dashboard are due to the contrib directory. Can we just turn
off contrib for that submission?