Difference between revisions of "Developer Meetings/20150324"
From Slicer Wiki
m (→Conclusions) |
m |
||
| Line 12: | Line 12: | ||
* Python conda - next steps: | * Python conda - next steps: | ||
| − | ** Create External_miniconda.cmake | + | ** Create External_miniconda.cmake |
| − | |||
** Add a variable named EXTERNAL_PYTHON_NAME that could take two values: python or miniconda | ** Add a variable named EXTERNAL_PYTHON_NAME that could take two values: python or miniconda | ||
| + | *** In the SuperBuild.cmake, an option named EXTERNAL_PYTHON_NAME could be added. By default, it would be set to "python" but could switch to "miniconda" | ||
** Projects like External_{CTK, VTK}.cmake would be updated to depend on ${EXTERNAL_PYTHON_NAME} | ** Projects like External_{CTK, VTK}.cmake would be updated to depend on ${EXTERNAL_PYTHON_NAME} | ||
** For now, let's consider only the case OpenSSL disabled. | ** For now, let's consider only the case OpenSSL disabled. | ||
Latest revision as of 19:07, 24 March 2015
Home < Developer Meetings < 20150324Contents
Updates
To discuss
- Extension contribution process - https://github.com/Slicer/ExtensionsIndex/pull/924#issuecomment-85539317
Todo
Conclusions
- Python conda - next steps:
- Create External_miniconda.cmake
- Add a variable named EXTERNAL_PYTHON_NAME that could take two values: python or miniconda
- In the SuperBuild.cmake, an option named EXTERNAL_PYTHON_NAME could be added. By default, it would be set to "python" but could switch to "miniconda"
- Projects like External_{CTK, VTK}.cmake would be updated to depend on ${EXTERNAL_PYTHON_NAME}
- For now, let's consider only the case OpenSSL disabled.
