Difference between revisions of "Developer Meetings/20130212"

Revision as of 19:21, 12 February 2013

ITKv4 enabled by default / SimpleITK updated to v0.6.1. See r21688
- Review list of existing issue (mantis tag: ITKv4)
Approach to display log on windows: http://slicer-devel.65872.n3.nabble.com/Windows-command-line-tp4027441p4027524.html
- Log to file ?
- Provide an other (application + Launcher) which would be console aware ?
Demo AutoRun for CLI modules (Julien, #2940)
Continuous integration
- Test takes way too long - What about creating a ctest LABEL named "fast" or one named "slow". It would then be easy to run integration tests: ctest -L fast or ctest -LE slow
Re-enable setup windows 32-bit nightly

@@ Line 1: / Line 1: @@
 == To discuss ==
 * ITKv4 enabled by default / SimpleITK updated to v0.6.1. See [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21688 r21688]
+** Review list of existing issue (mantis tag: ITKv4)
 * Approach to display log on windows: http://slicer-devel.65872.n3.nabble.com/Windows-command-line-tp4027441p4027524.html
 ** Log to file ?
 ** Provide an other (application + Launcher) which would be console aware ?
 * Demo AutoRun for CLI modules (Julien, [http://www.na-mic.org/Bug/view.php?id=2940 #2940])
+* Continuous integration
+** Test takes way too long - What about creating a ctest LABEL named "fast" or one named "slow". It would then be easy to run integration tests: <code>ctest -L fast</code> or <code>ctest -LE slow</code>
+* Re-enable setup windows 32-bit nightly
 == Conclusion ==