<div><br></div><div>I've put together some notes on my efforts to create a MacPorts port for ITK, see</div><div><a href="http://www.cmake.org/Wiki/ITK_MacPorts_Package_Maintainers">http://www.cmake.org/Wiki/ITK_MacPorts_Package_Maintainers</a></div>
<div><br></div><div>In a way, those notes will also apply to the vtk-devel port (I should make a wiki page for vtk-devel). For vtk-devel, the Portfile is here</div><div><a href="http://svn.macosforge.org/repository/macports/trunk/dports/graphics/vtk-devel/Portfile">http://svn.macosforge.org/repository/macports/trunk/dports/graphics/vtk-devel/Portfile</a></div>
<div><br></div><div>It's a lot to ask that you might learn something from reading this, but there are some sections in the Portfile that might be helpful. Look at the configure.args section to get an idea of how I setup cmake for the MacPorts configuration. (Note that these arguments are changed in the 'variants' sections.)</div>
<div><br></div><div>For python stuff, go down to the section on wrapping and look at the py25 variant and the functions that it calls, esp. <span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre-wrap; ">pyPostDestroot. <span class="Apple-style-span" style="font-family: arial; white-space: normal; font-size: small; ">The python wrapping required a lot of tweaks to get all the library links right, when using shared libs (dylib on OSX). Also look at the <span class="Apple-style-span" style="font-family: monospace; font-size: medium; white-space: pre-wrap; ">setPython <span class="Apple-style-span" style="font-family: arial; white-space: normal; font-size: small; ">function, because you could hack that to provide a custom python path for the wrapping.</span></span></span></span></div>
<div><br></div><div>It's not easy, but I hope that helps a little,</div><div>Darren</div><div><br></div><br><br><div class="gmail_quote">On Fri, Jan 29, 2010 at 5:12 AM, Smith, Mark E CTR USAF AFMC AEDC/ATA <span dir="ltr"><<a href="mailto:Mark.E.Smith@arnold.af.mil">Mark.E.Smith@arnold.af.mil</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Thanks for the info Darren. I have given up the attempt to build and install using the approach that I was attempting. I generally use Linux platforms for development, but I also have a Mac and I was attempting to build the same infrastructure on the Mac as I have on the Linux machines.<br>
<br>
I did not know that macports software could be installed in an alternate directory. I will look into it. However, I want to use my local Python installation, and that is where I have had difficulty.<br>
<div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: Darren Weber [mailto:<a href="mailto:darren.weber.lists@gmail.com">darren.weber.lists@gmail.com</a>]<br>
Sent: Thursday, January 28, 2010 2:09 PM<br>
To: Berk Geveci<br>
Cc: David Gobbi; Smith, Mark E CTR USAF AFMC AEDC/ATA; <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
Subject: Re: [vtkusers] Need Help Compiling VTK on OS X With Python Wrappers and a Local Python Installation<br>
<br>
<br>
You might try using macports without a root installation path. The default path is /opt/local/, but that can be changed. There may be some ports that contain instructions that require root access (perhaps apache, mysql, postgresql, etc. have system init scripts that require root access).<br>
<br>
Seems to me that your swimming a little too hard against the tide, esp. with .so libs on OSX/Darwin. How about you lighten your work load by asking your sys admin to install all your libraries? How about running your own system with root access (try Ubuntu)?<br>
<br>
Take care,<br>
Darren<br>
<br>
<br>
<br>
<br>
On Tue, Dec 22, 2009 at 10:27 AM, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:<br>
<br>
<br>
Same here. I have no idea how to build Python such that it generates<br>
.so libraries rather than .dylib. Even things like MacPorts, which are<br>
very Unixy, generate dylibs. I know for sure that there is no way of<br>
generating VTK libraries as .sos (Python modules on the other hand<br>
have the .so extension).<br>
<br>
-berk<br>
<br>
<br>
On Mon, Dec 21, 2009 at 5:58 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
> Well, ya got me then. Even when I build 3rd party unix non-framework<br>
> stuff on the Mac, including python, I still get dylibs. I didn't know<br>
> the mac loader would even recognize .so libraries.<br>
><br>
> David<br>
><br>
><br>
> On Mon, Dec 21, 2009 at 3:36 PM, Smith, Mark E CTR USAF AFMC AEDC/ATA<br>
> <<a href="mailto:Mark.E.Smith@arnold.af.mil">Mark.E.Smith@arnold.af.mil</a>> wrote:<br>
>> Except that when I built my local python installation I built it for a<br>
>> unix platform using .so libraries. No frameworks. No dylibs.<br>
>><br>
>> I think what I want is vtk built the same way, that is, for a unix<br>
>> platform.<br>
>><br>
>> -----Original Message-----<br>
>> From: David Gobbi [mailto:<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>]<br>
>> Sent: Monday, December 21, 2009 4:09 PM<br>
>> To: Smith, Mark E CTR USAF AFMC AEDC/ATA<br>
>> Cc: Berk Geveci; <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
>> Subject: Re: [vtkusers] Need Help Compiling VTK on OS X With Python<br>
>> Wrappers and a Local Python Installation<br>
>><br>
>> Hi Mark,<br>
>><br>
>> You're very close. You need to set the PYTHON_LIBRARY variable like so:<br>
>><br>
>> /System/Library/Frameworks/Python.framework/Python<br>
>><br>
>> Or like so:<br>
>><br>
>> /System/Library/Frameworks/Python.framework/Versions/2.5/Python<br>
>><br>
>> Of course using the correct path to your own python framework.<br>
>><br>
>> David<br>
>><br>
>><br>
>> On Mon, Dec 21, 2009 at 2:45 PM, Smith, Mark E CTR USAF AFMC AEDC/ATA<br>
>> <<a href="mailto:Mark.E.Smith@arnold.af.mil">Mark.E.Smith@arnold.af.mil</a>> wrote:<br>
>>> Yes, but the build process complains that it wants a file and not a<br>
>>> directory (at least on the PYTHON_LIBRARY setting). But since the<br>
>>> default just points to the framework directory I cannot tell what is<br>
>> the<br>
>>> correct thing to put here.<br>
>>><br>
>>> -----Original Message-----<br>
>>> From: Berk Geveci [mailto:<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>]<br>
>>> Sent: Monday, December 21, 2009 3:29 PM<br>
>>> To: Smith, Mark E CTR USAF AFMC AEDC/ATA<br>
>>> Cc: <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
>>> Subject: Re: [vtkusers] Need Help Compiling VTK on OS X With Python<br>
>>> Wrappers and a Local Python Installation<br>
>>><br>
>>> Did you try setting PYTHON_INCLUDE_DIR and PYTHON_LIBRARY to point to<br>
>>> your Python build? Note that these are advanced settings so you will<br>
>>> have to turn on advanced mode in CMake.<br>
>>><br>
>>> On Mon, Dec 21, 2009 at 2:14 PM, Smith, Mark E CTR USAF AFMC AEDC/ATA<br>
>>> <<a href="mailto:Mark.E.Smith@arnold.af.mil">Mark.E.Smith@arnold.af.mil</a>> wrote:<br>
>>>> I suspect that this question has been answered, but so for I have not<br>
>>>> been able to find the answer. I want to build and install VTK with<br>
>>>> Python wrappers on OS X. I must install VTK locally since I do not<br>
>>> have<br>
>>>> root access. I have a local installation of Python. When I build VTK<br>
>>> the<br>
>>>> system installation of Python and the libraries in the Python<br>
>>> framework<br>
>>>> are used. Thus, when I run my local python and attempt to import vtk<br>
>> I<br>
>>>> get an error like below.<br>
>>>><br>
>>>> Fatal Python error: Interpreter not initialized (version mismatch?)<br>
>>>><br>
>>>> I have LD_LIBRARY_PATH and DYLD_LIBRARY_PATH set to the path where my<br>
>>>> local Python libraries exist. I have my path set to pickup my local<br>
>>>> python executable and that is what is reported when I configure with<br>
>>>> ccmake. My local python installation does not have frameworks or<br>
>> dylib<br>
>>>> files. I am using VTK 5.4.2. Any suggestions how to solve this<br>
>>> problem?<br>
>>>><br>
>>>> Thanks<br>
>>>> _______________________________________________<br>
>>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>><br>
>>>> Visit other Kitware open-source projects at<br>
>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>><br>
>>>> Please keep messages on-topic and check the VTK FAQ at:<br>
>>> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
>>>><br>
>>>> Follow this link to subscribe/unsubscribe:<br>
>>>> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
>>>><br>
>>> _______________________________________________<br>
>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>><br>
>>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>><br>
>>> Please keep messages on-topic and check the VTK FAQ at:<br>
>> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
>>><br>
>><br>
><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
<br>
<br>
<br>
</div></div></blockquote></div><br>