User:Inorton/Slicer4:Misc - Revision history

Inorton at 17:23, 10 November 2010

2010-11-10T17:23:15Z

Inorton at 17:22, 10 November 2010

2010-11-10T17:22:00Z

Inorton at 15:11, 27 October 2010

2010-10-27T15:11:48Z

Inorton at 04:21, 23 October 2010

2010-10-23T04:21:27Z

Inorton: /* Paths */

2010-10-22T15:32:55Z

Paths

Inorton at 15:32, 22 October 2010

2010-10-22T15:32:20Z

Inorton at 14:47, 22 October 2010

2010-10-22T14:47:42Z

Inorton: Created page with 'In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:

%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacro…'

2010-10-21T21:25:41Z

Created page with 'In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here: <pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacro…'

New page

In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:
<pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacros.cmake</pre>

← Older revision		Revision as of 17:23, 10 November 2010
Line 33:		Line 33:
	/usr/lib/python2.6/plat-linux2		/usr/lib/python2.6/plat-linux2
	</pre>		</pre>
−
−	~~===nipype===~~

← Older revision		Revision as of 17:22, 10 November 2010
Line 33:		Line 33:
	/usr/lib/python2.6/plat-linux2		/usr/lib/python2.6/plat-linux2
	</pre>		</pre>
		+
		+	===nipype===

@@ Line 4: / Line 4: @@
 In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:
 <pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacros.cmake</pre>
-This is not available yet. Easy workaround script:
+This is not available yet. One possibility:
 <pre>
 import os
@@ Line 14: / Line 14: @@
 outfile.close()
 </pre>
-Then just execfile this script from the Slicer python shell and then source SetupSlicerPaths.sh.
+Then just execfile this script from the Slicer python shell and then source SetupSlicerPaths.sh.. but this doesn't quite work because some paths are missing and there is a lot of extra stuff. Needs to be hand-edited to get all the right paths.
 ===Module/Plugin Notes===
 *http://www.na-mic.org/Wiki/index.php/Events:CTK-Hackfest-2010/SlicerQtPluginArchitecture
 *http://stackoverflow.com/questions/43322/whats-safe-for-a-c-plug-in-system

@@ Line 1: / Line 1: @@
 ===Paths===
 In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:
@@ Line 10: / Line 12: @@
 for item in os.environ.keys():
          outfile.write(item + '=' + os.environ[item] + '\n')
 outfile.close()
 </pre>

@@ Line 2: / Line 2: @@
 In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:
 <pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacros.cmake</pre>
-This is not available yet. Easy workaround:
+This is not available yet. Easy workaround script:
 <pre>
 import os
@@ Line 13: / Line 13: @@
 outfile.close()
 </pre>
-Then just execfile from the Slicer python shell and source SetupSlicerPaths.sh.
+Then just execfile this script from the Slicer python shell and then source SetupSlicerPaths.sh.
 ===Module/Plugin Notes===
 *http://www.na-mic.org/Wiki/index.php/Events:CTK-Hackfest-2010/SlicerQtPluginArchitecture
 *http://stackoverflow.com/questions/43322/whats-safe-for-a-c-plug-in-system

← Older revision		Revision as of 14:47, 22 October 2010
Line 1:		Line 1:
	In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:		In Slicer3 the very useful "Slicer3SetupPaths" scripts are generated by a KWWidgets CMake macro script located here:
	<pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacros.cmake</pre>		<pre>%/Slicer3-SuperBuild/KWWidgets/CMake/KWWidgetsPathsMacros.cmake</pre>
		+	However, this doesn't appear to have anything KWW-specific so could move to Slicer4 with some tweaks.
		+
		+	=Module/Plugin Notes=
		+	*http://www.na-mic.org/Wiki/index.php/Events:CTK-Hackfest-2010/SlicerQtPluginArchitecture
		+	*http://stackoverflow.com/questions/43322/whats-safe-for-a-c-plug-in-system