[Insight-developers] Explicit instantiation linking issues on mac platform

[Hans Johnson]

Julien,

The Mac linking semantics are VERY strict.  I have seen this with other
packages also where a linux build works, but Mac build with approximately
the same version of gcc fails because the link information was not
completely defined.  It is my impression that the Mac linking stage requires
that all symbols (whether used or not) must be defined, whereas the linux
builds only require that the used symbols be linked.

Hans
 


On 9/7/06 11:15 AM, "Julien Jomier" <julien.jomier at kitware.com> wrote:

> Hans,
> 
> Sure. I'll make the changes as soon as I get cvs write access.
> This is strange that it never came up on the dashboard before.
> 
> Julien
> 
> Hans Johnson wrote:
>> Brad:  Adding the explicit source files directly to the ITKCommon is
>> definitely my preference, and I think that it makes linking more robust and
>> easier to understand.
>> 
>> Julien:  Would you be able to make this change after the cvs repository is
>> opened back up?
>> 
>> Thanks,
>> Hans
>> 
>> 
>> 
>> 
>> On 9/7/06 8:30 AM, "Brad King" <brad.king at kitware.com> wrote:
>> 
>>> Hans Johnson wrote:
>>>>>>>> IF(ITK_EXPLICIT_INSTANTIATION)
>>>>>>>>   TARGET_LINK_LIBRARIES (ITKCommon ITKCommonExplicit)
>>>>>>>> ENDIF(ITK_EXPLICIT_INSTANTIATION)
>>>>> Do you get the error when compiling ITK or an external program using ITK?
>>>> The problems occur in compiling the Testing and Examples directories under
>>>> ITK.
>>> The problem is that symbols in ITKCommonExplicit need symbols in
>>> ITKCommon.  The source files for ITKCommonExplicit should just be added
>>> to the ITKCommon library directly.
>>> 
>>> -Brad
>> 
>> _______________________________________________
>> Insight-developers mailing list
>> Insight-developers at itk.org
>> http://www.itk.org/mailman/listinfo/insight-developers
>> 
>