Difference between revisions of "Developer Meetings/20170711"

From Slicer Wiki
Jump to: navigation, search
(Created page with "{{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this p...")
 
Line 13: Line 13:
 
* Transition to C++11
 
* Transition to C++11
 
* MacOSX: Update minimum required version to 10.9
 
* MacOSX: Update minimum required version to 10.9
 +
** Released in Oct 2013
 +
** https://en.wikipedia.org/wiki/OS_X_Mavericks
  
 +
From Max / Related to VT8 transition
 +
 +
<pre>
 +
Have not tested on Mac due to complications with respect to Qt, VTK, C++11, deployment targets, and the standard library
 +
 +
VTK8 and Qt 5.7+ require C++11. I think it may be necessary to have Slicer build with C++11 at this point,
 +
although the Linux build has worked so far without explicitly enabling it.
 +
 +
On Mac, building VTK while targeting 10.7 requires manually specifying CMAKE_CXX_FLAGS=-stdlib=libc++, because the version
 +
of libstdc++ that Apple ships doesn't support C++11. Slicer will likely need to handle this unless we target 10.9.
 +
</pre>
  
 
= Conclusion =
 
= Conclusion =

Revision as of 13:27, 11 July 2017

Home < Developer Meetings < 20170711


Update

To Discuss

From Max / Related to VT8 transition

Have not tested on Mac due to complications with respect to Qt, VTK, C++11, deployment targets, and the standard library

VTK8 and Qt 5.7+ require C++11. I think it may be necessary to have Slicer build with C++11 at this point, 
although the Linux build has worked so far without explicitly enabling it.

On Mac, building VTK while targeting 10.7 requires manually specifying CMAKE_CXX_FLAGS=-stdlib=libc++, because the version
of libstdc++ that Apple ships doesn't support C++11. Slicer will likely need to handle this unless we target 10.9.

Conclusion