<br><div class="gmail_quote">On Tue, Jun 30, 2009 at 3:29 AM, Badri Roysam <span dir="ltr"><<a href="mailto:roysam@ecse.rpi.edu">roysam@ecse.rpi.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yes, as of today, the FARSIGHT build wiki as written is by and large an ITK build. There is<br>
another page under construction that is much more FARSIGHT specific. We plan to clean up<br>
all this confusion soon.<br>
<br>
<a href="http://www.farsight-toolkit.org/wiki/FARSIGHT_HowToBuild" target="_blank">http://www.farsight-toolkit.org/wiki/FARSIGHT_HowToBuild</a><br>
</blockquote><div><br><br>Oh cool, thanks!<br><br>Although the details of the cmake settings and the Qt build may vary from the instructions (which might be important in some cases), it might be possible to satisfy the dependencies on OSX using MacPorts, as follows:<br>
<br>sudo port install cmake<br>sudo port install qt4-mac<br>
# OR<br>#sudo port install qt4-x11<br>
sudo port install vxl<br>sudo port install InsightToolkit +wrap<br>sudo port install vtk-devel<br><br>If you need to check or modify any of these port configurations, that's possible. Take a look at this ITK wiki page for tips, especially the tips on local repositories:<br>
<a href="http://www.vtk.org/Wiki/ITK_MacPorts_Package_Maintainers">http://www.vtk.org/Wiki/ITK_MacPorts_Package_Maintainers</a><br>It took me about 1-2 days to learn the basics of developing custom MacPorts. Sometimes your custom tweaks should become part of the standard port, so you just submit a patch to the trac system and see what happens. You might need to refresh your tcl, as Portfiles are basically tcl scripts.<br>
<br>Then configure and build farsight, trying to link against libraries installed somewhere into /opt/local/ (the default prefix for MacPorts). If I can find and justify the time, I may try to configure a MacPort for the farsight build, which would try to take care of everything (it's not likely to happen soon).<br>
<br>Note that InsightToolkit has it's own vxl build (maybe that will change someday, to link against the vxl port). So, you might have to double check how your farsight build links to vxl libs if both are installed.<br>
<br>I hope that will help a little to get farsight onto OSX for all the mac freaks ;-)<br><br></div></div>Take care,<br>Darren<br><br>