<br>MacPorts now contains the latest update of InsightToolkit (@3.14.0), in a port of the same name.<br><br>To best of my knowledge, this new release can co-exist with a prior release, now called InsightToolkit312 @ 3.12.0. This prior release was modified so that it will install along with an installation of InsightToolkit (@3.14.0). In my testing of this process, I first had to uninstall InsightToolkit (@3.12.0), then upgrade to InsightToolkit (@3.14.0), and finally install (or perhaps reinstall) the prior release port, now called InsightToolkit312.<br>
<br>The command line looks like this:<br><br>sudo uninstall InsightToolkit<br>sudo port selfupdate<br>sudo port install InsightToolkit<br>sudo port install InsightToolkit312<br>
<br>If your lucky, you might be able to shorten the above to this:<br><br>sudo port selfupdate<br>
sudo port upgrade InsightToolkit<br>
sudo port install InsightToolkit312<br>
<br>If you have 3.12.0 installed, but you don't need 3.12.0 at all, then just try this:<br><br>sudo port selfupdate<br>
sudo port upgrade InsightToolkit<br>
<br>For a new installation of InsightToolkit, all you need is:<br><br>sudo port selfupdate<br>
sudo port install InsightToolkit<br>
<br>By default, you get documentation and shared libraries with wrapping for java, tcl, and python2.5.<br><br>During testing, I also built and installed all the examples and the testing stuff, which looks like this:<br><br>
sudo port selfupdate<br>
sudo port install InsightToolkit +examples +testing<br>
<br>Be warned, this build and install is one to run overnight. For a detailed progress indicator, you can try:<br><br>sudo port -d install InsightToolkit +examples +testing<br>
<br>The build and install works, but the functionality has not been extensively tested (not sure how to run all the tests). If you discover any problems with the build and installation process, that could be a MacPorts bug, for which you can submit a bug report at <a href="http://trac.macports.org/">http://trac.macports.org/</a>. If you discover functional bugs after the installation, that's probably an upsteam issue to fix in the toolkit itself.<br>
<br>Take care,<br>Darren<br><br><br>PS.<br><br>If there are features that are not enabled, but should be, please let me know. All the build and install process is "kinda" documented in the Portfile, which you can read like a pseudo tcl-script. You can see all the details of these ports in these files in the MacPorts rsync:<br>
<br>/opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/graphics/InsightToolkit/Portfile">rsync.macports.org/release/ports/graphics/InsightToolkit/Portfile</a><br>/opt/local/var/macports/sources/<a href="http://rsync.macports.org/release/ports/graphics/InsightToolkit312/Portfile">rsync.macports.org/release/ports/graphics/InsightToolkit312/Portfile</a><br>
<br>The svn browser is also available, at:<br><a href="http://svn.macosforge.org/repository/macports/trunk/dports/graphics/InsightToolkit/Portfile">http://svn.macosforge.org/repository/macports/trunk/dports/graphics/InsightToolkit/Portfile</a><br>
<a href="http://svn.macosforge.org/repository/macports/trunk/dports/graphics/InsightToolkit312/Portfile">http://svn.macosforge.org/repository/macports/trunk/dports/graphics/InsightToolkit312/Portfile</a><br>
<br>