SET (ITK_DIR /opt/local/lib/InsightToolkit-3.14) Once it's installed, your CMakeLists.txt file(s) may have to set the ITK_DIR to be certain about linking, i.e.: If you want to edit and install your own custom Portfiles, you can follow these instructions: There is a man page on port for all the details on how to use it. You can also view properties and content of ports using: opt/local/var/macports/sources//release/ports/graphics/InsightToolkit312/Portfile opt/local/var/macports/sources//release/ports/graphics/InsightToolkit/Portfile Those Portfiles are in the subversion development tree and they make their way into a release that is synced to your MacPorts installation: ![]() All the build and install configurations are coded in the Portfile. It may be possible to resolve this using some environment variable settings, but it would be nice to avoid that, if possible, in preference to specific cmake (or WrapITK) configurationįor the curious, the details of the port are all in the pseudo tcl script called the 'Portfile'. rather than the MacPorts framework in /opt/local/Library/. Despite setting specific paths to the python2.6 library in macports, the cmake or WrapITK configuration process automatically redefined the library variables to '-framework Python' and that was automatically resolved to the Apple framework in /Library/. It might be possible to get the wrapping working for python2.6, but I encountered some weird results when trying to set the configuration options for the python2.6 framework library in MacPorts. jnilib files, so please enlighten me if you want java wrapping to work, if it's not working already). jnilib files, but this assumes those files can be modified by install_name_tool (actually, I have no idea how to work with. The port does try to fix library references in the. The wrapper also includes java, but I've not tested it. On my system, at least, the itkwish binary works and the 'import itk' works for python2.5. Further hacks were required for the itkwish shell script in $prefix/bin/itkwish and the actual binary in WrapITK/bin/itkwish. Some port hacks were required to get all the rpath settings right for the Tcl. This port is available as InsightToolkit312. InsightToolkit MacPorts port for InsightToolkit (ITK) is also available at release 3.12.0. This port is available as InsightToolkit314. InsightToolkit MacPorts port for InsightToolkit (ITK) is also available at release 3.14.0. It should be possible to shorten the above to this: For example, that process looked like this:Īfter some testing and modifications to the ports, the process may be easier. Prior releases should be available as 'InsightToolkit$. The port name 'InsightToolkit' should be maintained at the latest release version. If a prior release is required, that should be possible to create. The MacPorts for InsightToolkit (ITK) are available at several recent release versions (3.12.0, 3.14.0, and 3.16.0 at Sep 2009). You can learn the specifics about MacPorts from:įor a port installed, to find out where everything is, useĪlso, if there is a file installed, the port that installed it can be identified by using For the InsightToolkit ports, you can contact me, Darren Weber: dweber_AT_ In general, the best way to contact a port maintainer is to file a trac ticket at.
0 Comments
Leave a Reply. |