[Insight-developers] Clang Warnings about in-class static initializers...
Williams, Norman K
norman-k-williams at uiowa.edu
Fri Dec 16 14:37:01 EST 2011
It appears that this is a configuration issue. The vnl CMakeLists.txt
configures vcl_config_compiler.h.in
which defines VCL_STATIC_CONST_INIT_INT, which is set or unset based on
compiler tests. There are 3 choices in order of preferability:
1. in-class static initializers are supported.
2. in-class static initializers are not supported, and are a compiler
error.
3. in-class static initializers are supported, but when encountered, the
compiler issues a warning.
What could remedy the situation without involving any modifications to VNL
would be if theres a way to force VCL_STATIC_CONST_INIT_INT to be false/0
when CLang is used.
On 12/16/11 10:13 AM, "Sean McBride" <sean at rogue-research.com> wrote:
>On Fri, 16 Dec 2011 16:07:35 +0000, Williams, Norman K said:
>
>>The CLang I built was the SVN trunk as of yesterday.
>>
>>I do get all the way through building ITK4, so VXL is compiling on Lion,
>>both with gcc-llvm-4.2 and CLang.
>
>Sorry, I should have been clearer... The (subset?) of vxl that's in ITK
>works fine when one builds ITK with clang. But building vxl all by
>itself fails on the newest Lion. Not sure really why it's not a problem
>for ITK. Here's the thread if you're interested:
><http://sourceforge.net/mailarchive/forum.php?thread_name=20111201165654.1
>725884470%40mail.rogue-research.com&forum_name=vxl-users>
>
>>I am not on the VXL mailing list; it's kind of strange that they'd
>>persist
>>in using a language feature that's non standard, particularly when it's
>>so
>>easy to do it correctly.
>
>Dunno. I don't follow vxl closely...
>
>--
>____________________________________________________________
>Sean McBride, B. Eng sean at rogue-research.com
>Rogue Research www.rogue-research.com
>Mac Software Developer Montréal, Québec, Canada
>
>
________________________________
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.
________________________________
More information about the Insight-developers
mailing list