Sean,

I've redone the build process and noticed that Rtree "setup.py install" 
indeed requires spatialindex.lib. Previously I just assumed it did not 
need it, since resulting _rtree.pyd did not import anything from the DLL.

Anyway, even though spatialindex (I'm using v1.3.2) build process 
produces DLL and import library, which I copy to Rtree directory prior 
to invoking setup.py, the fact is that resulting _rtree.pyd does not 
import any symbols from the DLL. As I can see, this could only happen if 
Rtree only uses inline functions (if any) from spatialindex. My 
_rtree.pyd is about 150kb in size, if that has any significance.

Jaakko

Sean Gillies wrote:
> Hi Jaakko,
>
> In the 0.3 release we stopped carrying the spatialindex library within
> the Rtree source and started depending on the library installed
> seperately. Do you not have the spatialindex DLL on your system? If the
> tests are passing without it, I should fix them at the very least!
>
> Sean
>
> Jaakko Salli wrote:
>   
>> Hi Sean,
>>
>> I'm wondering if spatialindex library is mandatory for Rtree (readme.txt 
>> and your post is not entirely clear about this). I'm asking this because 
>> I thought I built Rtree 0.4.1 on Windows just fine. However, now I'm 
>> wondering if I did it correctly after all as my _rtree.pyd does not link 
>> to spatialindex DLL. Instead it only seemed to need spatialindex headers 
>> during compilation time. Regardless, library seems to work just fine and 
>> benchmarks.py and doc_tests.py run successfully.
>>
>> Does this sound right to you, or did I manage to build somehow lacking 
>> version of the library?
>>
>> Thanks,
>>   Jaakko
>>
>> Sean Gillies wrote:
>>     
>>> Hi all,
>>>
>>> If I remember correctly, the blocker for Rtree 1.0
>>>
>>>   http://trac.gispython.org/lab/milestone/Rtree%201.0
>>>
>>> is a unwritten want to have the Spatialindex library build on Windows.
>>> I'd like to push Rtree ahead regardless, with Windows support added
>>> post-1.0. Thoughts?
>>>
>>> Sean
>>> _______________________________________________
>>> Community mailing list
>>> [email protected]
>>> http://lists.gispython.org/mailman/listinfo/community
>>>
>>>   
>>>       
>> _______________________________________________
>> Community mailing list
>> [email protected]
>> http://lists.gispython.org/mailman/listinfo/community
>>
>>     
>
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.gispython.org/mailman/listinfo/community
>
>   

_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community

Reply via email to