From: Wheeler, F. W (G. Research) <wh...@cr...> - 2009-03-26 21:26:45
|
I turned off core/vidl (BUILD_CORE_VIDEO=OFF) for the Borland VXL dashboard build. There were build errors and I suspect nobody cares to make vidl2 compile under bcc. If I'm wrong and someone wants to see those errors, just let me know and I'll turn it back on. Fred |
From: Matthew L. <mat...@gm...> - 2009-03-26 23:40:16
|
Fred, I'm not surprised that Borland has problems with vidl2. vidl2 uses a lot of template trickery that pushes the C++ standard to the limits of what many compilers support. Maybe it's time to review our policies on core libraries. What compilers do we officially support? Does vidl2 need to compile on Borland to be in core? I'd like to see VXL start to allow more modern aspects of the C++ standard in VXL core. I'd like to be able to use anything from the C+ +98 standard, especially if it is supported by all versions of gcc and MSVC++ from the last 5 years. I can see the need for ensuring that older core libraries like vnl, vil, and vgl build on more obscure compilers. So maybe we could allow more modern code only in some newer core libraries that can easily be disabled in CMake. This discussion applies to vpdl (especially vpdl/vpdt) as well as vidl2. The vpdl code pushes the limits even more so than vidl2. At some point soon I'd like to enable it with a BUILD_CORE_PROBABILITY option that defaults to ON only for dashboard builds. I can't wait to see what kind of havoc that will unleash on the dashboard. Matt On Mar 26, 2009, at 5:25 PM, Wheeler, Frederick W (GE, Research) wrote: > > I turned off core/vidl (BUILD_CORE_VIDEO=OFF) for the Borland VXL > dashboard build. There were build errors and I suspect nobody cares > to > make vidl2 compile under bcc. If I'm wrong and someone wants to see > those errors, just let me know and I'll turn it back on. > > Fred > > ------------------------------------------------------------------------------ > _______________________________________________ > Vxl-maintainers mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers |
From: Wheeler, F. W (G. Research) <wh...@cr...> - 2009-03-27 12:40:49
|
Matthew Leotta wrote: > I'm not surprised that Borland has problems with vidl2. > vidl2 uses a lot of template trickery that pushes the C++ > standard to the limits of what many compilers support. Maybe > it's time to review our > policies on core libraries. What compilers do we officially > support? > Does vidl2 need to compile on Borland to be in core? I don't see why vidl2 would need to compile on Borland. Here is the main reason bcc is still on the dashboard ... Brad King wrote on 2007-06-27: > 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? > > -Brad (https://sourceforge.net/mailarchive/message.php?msg_id=46827137.2000201 %40kitware.com) I suggest 1. we ensure vnl, vnl_algo, vcl, netlib compile on borland, 2. we don't worry about borland for any other libraries, 3. other libraries that happen to compile on borland will be included in the dashboard build, but dropped if they start having persistent borland compiler problems. Fred |
From: Matthew L. <mat...@gm...> - 2009-03-27 12:45:44
|
On Mar 27, 2009, at 8:39 AM, Wheeler, Frederick W (GE, Research) wrote: > > I suggest 1. we ensure vnl, vnl_algo, vcl, netlib compile on > borland, 2. > we don't worry about borland for any other libraries, 3. other > libraries that happen to compile on borland will be included in the > dashboard build, but dropped if they start having persistent borland > compiler problems. > fine with me. Matt |