Difference between revisions of "Developer Meetings/20130212"

From Slicer Wiki
Jump to: navigation, search
Line 13: Line 13:
 
* Re-enable setup windows 32-bit nightly
 
* Re-enable setup windows 32-bit nightly
 
* CMake'ification / OpenSSL integration: No progress due to integration of ITKv4.
 
* CMake'ification / OpenSSL integration: No progress due to integration of ITKv4.
 +
* Extensions
 +
** Considering disabling extension ukftractography. See https://github.com/pnlbwh/ukftractography/issues/3
 +
*** Adding extension named "Boost" would probably help: https://github.com/pnlbwh/ukftractography/issues/2
 +
** Will very probably add an extension named "JsonCpp". See [https://github.com/chrismullins/ExtensionsIndex/commit/987fa3008e2b7f7f5ff49f80a4e6c736d66499f9 JsonCpp.s4ext]
  
 
== Conclusion ==
 
== Conclusion ==

Revision as of 20:58, 12 February 2013

Home < Developer Meetings < 20130212

To discuss

  • 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
    • Python self test are very long. Does it make sens to run them continously. What about one time a week ? During the weekend ?
  • Refactor of Python self test
    • Duplicated code :( ... => maintenance hell. See third point reported here.
  • Re-enable setup windows 32-bit nightly
  • CMake'ification / OpenSSL integration: No progress due to integration of ITKv4.
  • Extensions

Conclusion