[Insight-developers] trying to fix mac warnings

[Williams, Norman K]

I don't think that it should be that annoying to conditionally add files
to a library based on platform.  All the 'pain' is in writing the
predicate for the platform.

Though that could be painful;  what you'd know ideally is

1. If you're on windows (perhaps just the mis-named WIN32 variable?).
2. If you're actually building 64bit targets (????).

#2 being harder because you can build 32-bit on 64-bit machines.

On 2/23/11 12:29 PM, "Johnson, Hans J" <hans-johnson at uiowa.edu> wrote:

>I've seen this type of behavior when conditional code exists for only one
>platform, but not another.  This file is an empty file on all platforms
>except WIN64.
>
>There are two ways I've worked around this:
>Clean but painful:  only complile this conditionally when WIN64 is needed.
>Easy but ugly:      make a new function that is always compiled called
>"void
>i_am_a_dummyfunction_to_silence_compiler_warning_vnl_c_vector_longlong_cxx
>(
>void) {};
>
>
>Hans
>
>
>-----Original Message-----
>From: Sean McBride <sean at rogue-research.com>
>Organization: Rogue Research Inc.
>Date: Wed, 23 Feb 2011 13:22:54 -0500
>To: Mark Roden <mmroden at gmail.com>, ITK <insight-developers at itk.org>
>Subject: Re: [Insight-developers] trying to fix mac warnings
>
>On Wed, 23 Feb 2011 10:04:36 -0800, Mark Roden said:
>
>>/usr/bin/ranlib: file:
>>../../bin/libitkvnl_inst.a(vnl_c_vector+longlong-.cxx.o) has no
>>symbols
>
>I've seen these warnings a lot, building VTK, ITK, GDCM, etc.  When
>you're trying to repro are you building as static libs or dylibs?  It
>may need to be the former.  It could be helpful to inspect the library
>with nm (see man nm).
>
>--
>____________________________________________________________
>Sean McBride, B. Eng                 sean at rogue-research.com
>Rogue Research                        www.rogue-research.com
>Mac Software Developer              Montréal, Québec, Canada
>
>
>_______________________________________________
>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
>
>
>
>________________________________
>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.
>________________________________
>_______________________________________________
>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



________________________________
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.
________________________________