<div>Hi David,</div>Thankyou so much for this explanation. It makes everything really clear now. I finally understand the Python setup.<div>Regards</div><div> Andrew</div><div><br><br><div class="gmail_quote">On Thu, May 3, 2012 at 3:19 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The "D" stands for .dylib, which is the shared library suffix on OS X.<br>
<br>
Originally, the python modules had a ".dll" suffix on Windows and<br>
a ".so" suffix on Linux. This meant that python modules were really<br>
just shared libraries with a special python "init" function. As far as<br>
the linker was concerned, there was no difference between a python<br>
module and a shared library.<br>
<br>
With OS X, shared libraries end in ".dylib" and python modules end<br>
in ".so", so it was no longer possible to have the python modules<br>
act as both modules, and as link libraries. This distinction was also<br>
recognized by cmake (though I forget in what version). Also, on<br>
Windows, python started to require that python modules end in ".pyd"<br>
as of python 2.5.<br>
<br>
To support OS X (and later Windows), it was necessary to break the<br>
python wrappers into two parts: one part that is a shared library (the<br>
"D" part, which is a .dylib on OS X, hence the "D"), and another part<br>
that is a python module.<br>
<span class="HOEnZb"><font color="#888888"><br>
- David<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Wed, May 2, 2012 at 11:00 AM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>> wrote:<br>
> I think the 'D' must stand for Dependency. It is a bit confusing, because a<br>
> D at the end of library name usually means Debug.<br>
><br>
> Pat<br>
><br>
><br>
> On Wed, May 2, 2012 at 9:31 AM, Jean-Christophe Fillion-Robin<br>
> <<a href="mailto:jchris.fillionr@kitware.com">jchris.fillionr@kitware.com</a>> wrote:<br>
>><br>
>> FYI - The oldest commit I found referencing "PythonD" is the following one<br>
>> [1], it explains why there is a separation into a Python and PythonD<br>
>> library.<br>
>><br>
>> Hth<br>
>> Jc<br>
>><br>
>> [1] <a href="http://vtk.org/gitweb?p=VTK.git;a=commit;h=56ca4f8198" target="_blank">http://vtk.org/gitweb?p=VTK.git;a=commit;h=56ca4f8198</a><br>
>><br>
>><br>
>> On Wed, May 2, 2012 at 9:21 AM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>> wrote:<br>
>>><br>
>>> Hi Andrew,<br>
>>><br>
>>> For each python module there should be two libraries:<br>
>>><br>
>>> libvtkCommonCorePythonD.so<br>
>>> vtkCommonCorePython.so<br>
>>><br>
>>> The second library is the python c extension module (and it's probably in<br>
>>> a different output directory.) I forget was the 'D' stands for, but it<br>
>>> doesn't mean debug.<br>
>>><br>
>>> Pat<br>
>>><br>
>>><br>
>>> On Tue, May 1, 2012 at 11:30 PM, Andrew Maclean<br>
>>> <<a href="mailto:andrew.amaclean@gmail.com">andrew.amaclean@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi Marcus,<br>
>>>> Sorry the last message was garbled.<br>
>>>> I was reviewing the dlls in the windows build of VTK 6.0 and noticed<br>
>>>> that all the python dlls have a D suffix in the release build,<br>
>>>> e.g vtkAMRCorePythonD-6.0.dll, similarly on Linux e.g<br>
>>>> vtkAMRCorePythonD *.so*<br>
>>>><br>
>>>> I did a quick scan through the CMakeLists.txt files but I can't see<br>
>>>> where D suffix is being added for the release versions.<br>
>>>><br>
>>>> Is it intentional that these files all have the D suffix for release<br>
>>>> versions?<br>
>>>><br>
>>>> Regards<br>
>>>> Andrew<br>
>>>><br>
>>>> --<br>
>>>> ___________________________________________<br>
>>>> Andrew J. P. Maclean<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<br>
>>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>><br>
>>>> Follow this link to subscribe/unsubscribe:<br>
>>>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>><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<br>
>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> <a href="tel:%2B1%20919%20869%208849" value="+19198698849">+1 919 869 8849</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<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>