[Insight-developers] ITK version numbers

[Matt McCormick]

We already have a .cxx file with an API in itkVersion.{h,cxx}.  The
pre-processors macros will need to be removed from both the
itkConfigure.h and itkVersion.h.  Then, itkVersion.cxx will need to
include a new header that has the macros.

Matt

On Mon, Dec 19, 2011 at 5:22 PM, Bradley Lowekamp
<blowekamp at mail.nih.gov> wrote:
> We need the defines in some header, so we can use the pre-processor to say if v4 do this new thing, otherwise do this legacy thing. I think itkVersion.h is the place for this preprocessor definition.
>
> Brad L.
>
> On Dec 19, 2011, at 5:16 PM, Johnson, Hans J wrote:
>
>> I agree with Brad King.  It is best to put this into a .cxx file and
>> provide an API.
>>
>> Hans
>>
>> --
>> Hans J. Johnson, Ph.D.
>> hans-johnson at uiowa.edu
>> Assistant Professor of Psychiatry
>> University of Iowa Carver College of Medicine
>> W278 GH, 200 Hawkins Drive
>>
>> Iowa City, Iowa 52242
>> Phone:  319-353-8587
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Brad King <brad.king at kitware.com>
>> Date: Mon, 19 Dec 2011 17:09:13 -0500
>> To: Matt McCormick <matt.mccormick at kitware.com>
>> Cc: Bradley Lowekamp <blowekamp at mail.nih.gov>, ITK
>> <insight-developers at itk.org>, Hans Johnson <hans-johnson at uiowa.edu>, Luis
>> Ibanez <luis.ibanez at kitware.com>
>> Subject: Re: [Insight-developers] ITK version numbers
>>
>> On Mon, Dec 19, 2011 at 5:06 PM, Matt McCormick
>> <matt.mccormick at kitware.com> 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.
>>
>> We should keep the configured version number in a .cxx file and provide an
>> API to retrieve it at runtime.
>>
>> -Brad K
>>
>>
>>
>> ________________________________
>> Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
>> ________________________________
>