[Insight-developers] ITK version numbers

Bradley Lowekamp blowekamp at mail.nih.gov
Mon Dec 19 17:14:13 EST 2011


Actually I think it is touching the itkConfigure.h.in file is the problem.

If we moved:
#define ITK_VERSION_MAJOR @ITK_VERSION_MAJOR@
#define ITK_VERSION_MINOR @ITK_VERSION_MINOR@
#define ITK_VERSION_PATCH @ITK_VERSION_PATCH@
#define ITK_VERSION_STRING "@ITK_VERSION_STRING@"

to a itkVersion.h.in and removed it from itkConfigure.h. We would OK.

This would have the non-backwards compatible change of requiring users to include itkVersion.h, if you want a the version number. I think this is well worth it.

Brad L.

On Dec 19, 2011, at 5:06 PM, Matt McCormick wrote:

> This is a very good point.  We have itkVersion.h in ITKCommon that is
> included by many of the IO files, which will cause full rebuilds for
> most of WrapITK, SimpleITK, and ITK if trying to use ccache.
> 
> On Mon, Dec 19, 2011 at 5:00 PM, Bradley Lowekamp
> <blowekamp at mail.nih.gov> wrote:
>> What are the dependencies on the cmake version number?
>> 
>> I just updated SimpleITK from using ITKrc5 to v4.0 and every thing is having to be rebuild, and I am not getting any ccache hits.
>> 
>> I think it would be bad if we use dates and too many things depend on that causing everything to be rebuild and rendering ccache not useful. Just think of the WrapITK a dashboard systems.
>> 
>> Brad L.
>> 
>> 
>> On Dec 19, 2011, at 4:50 PM, Brad King wrote:
>> 
>>> On 12/19/2011 4:45 PM, Bill Lorensen wrote:
>>>> With long release cycles like VTK I think the date is important.
>>>> 
>>>> This is certainly true with the wiki examples where we want to have
>>>> the examples work for released and non-released versions. I don't see
>>>> the harm in having a patch based on date for the odd versions between
>>>> releases. For even number releases, the patch number should increment
>>>> from 0.
>>> 
>>> Clearly we need a granular version number during development cycles.
>>> 
>>> What David is saying is that it should not be based on a daily commit.
>>> He and I have been brainstorming ways to get rid of it from CMake.
>>> I discussed some of the problems in other responses in this thread.
>>> 
>>> -Brad
>>> _______________________________________________
>>> Powered by www.kitware.com
>>> 
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>> 
>>> Kitware offers ITK Training Courses, for more information visit:
>>> http://kitware.com/products/protraining.html
>>> 
>>> Please keep messages on-topic and check the ITK FAQ at:
>>> http://www.itk.org/Wiki/ITK_FAQ
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.itk.org/mailman/listinfo/insight-developers
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>> 
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers



More information about the Insight-developers mailing list