Difference between revisions of "Developer Meetings/20140204"
From Slicer Wiki
| Line 2: | Line 2: | ||
* Upgrade ITK Version: v4.5.0++ w/ patches on release branch | * Upgrade ITK Version: v4.5.0++ w/ patches on release branch | ||
| + | |||
| + | * How to handle libc++ on OSX? | ||
| + | ** The std library can be detected with a normal try_compile. | ||
| + | *** It must be BEFORE any other caching try_compiles. | ||
| + | *** The stdlib can be set as in the CMake variables. | ||
| + | ** Do we need to detect what Qt is compile against? and set the standard lib as a required flag across super build projects? | ||
| + | ** How should this be handled in SimpleITK's super build and non-super builds? | ||
* Enabling Threading in SimpleITK, and other Python Threading issues. | * Enabling Threading in SimpleITK, and other Python Threading issues. | ||
** Options for Qt Event loop which unlock the Python GIL | ** Options for Qt Event loop which unlock the Python GIL | ||
** Generalizing Threading Logic into a reusable python base class | ** Generalizing Threading Logic into a reusable python base class | ||
| − | |||
| − | |||
* | * | ||
Revision as of 16:32, 4 February 2014
Home < Developer Meetings < 20140204To discuss
- Upgrade ITK Version: v4.5.0++ w/ patches on release branch
- How to handle libc++ on OSX?
- The std library can be detected with a normal try_compile.
- It must be BEFORE any other caching try_compiles.
- The stdlib can be set as in the CMake variables.
- Do we need to detect what Qt is compile against? and set the standard lib as a required flag across super build projects?
- How should this be handled in SimpleITK's super build and non-super builds?
- The std library can be detected with a normal try_compile.
- Enabling Threading in SimpleITK, and other Python Threading issues.
- Options for Qt Event loop which unlock the Python GIL
- Generalizing Threading Logic into a reusable python base class
- Adding Qt Support for Apple Retina ( very pretty fonts )
