Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

built-in spatialindex conflicts with external libspatialindex #13567

Closed
qgib opened this issue Feb 19, 2011 · 9 comments
Closed

built-in spatialindex conflicts with external libspatialindex #13567

qgib opened this issue Feb 19, 2011 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins

Comments

@qgib
Copy link
Contributor

qgib commented Feb 19, 2011

Author Name: rustychris - (rustychris -)
Original Redmine Issue: 3507
Affected QGIS version: master
Redmine category:python_plugins


libspatialindex is used by the python rtree module, but when this module is loaded from within a QGIS python plugin, the symbols from the builtin copy of spatialindex collide and render the python rtree module inoperable.

How to reproduce: install the rtree python module. Start QGIS and open a python console:

>>> import rtree
>>> p = rtree.index.Property()
>>> p.set_storage(0)
True
>>> p.get_storage()
1
>>>

Stepping through in gdb shows that libspatialindex.so:Tools::PropertySet::getProperty is shadowed by a function of the same name in libqgis_core.so.

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2011

Author Name: Volker Fröhlich (@volter)


By updating the [[SpatialIndex]] wrapper and amending CMakeLists and creating a Cmake script, I managed to build QGIS with a systemwide libspatialindex.

Wonder proposed to update the shipped copy of [[SpatialIndex]] and update the wrapper, so the user has the choice to use either lib.

Doing so, would help your problem, I suppose.

I can provide a patch, but I'm not a 100% sure, everything works correct or that my patch is sound, as I am no C++ programmer. Maybe we should do that after 1.7.

@qgib
Copy link
Contributor Author

qgib commented Mar 10, 2011

Author Name: Borys Jurgiel (@borysiasty)


The sooner you send it, the sooner JEF&Marco&Tim&Martin will be able to review it ;-)

@qgib
Copy link
Contributor Author

qgib commented Jul 25, 2011

Author Name: Volker Fröhlich (@volter)


Please see #14093


  • pull_request_patch_supplied was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.0 to Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Apr 16, 2012

Author Name: Paolo Cavallini (@pcav)


  • version was configured as master
  • crashes_corrupts_data was configured as 0
  • fixed_version_id was changed from Version 1.7.4 to Version 1.8.0

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.8.0 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Sep 16, 2012

Author Name: Borys Jurgiel (@borysiasty)


  • assigned_to_id removed Borys Jurgiel

@qgib
Copy link
Contributor Author

qgib commented Jun 28, 2014

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - Lower Priority

@qgib
Copy link
Contributor Author

qgib commented Nov 20, 2015

Author Name: Médéric RIBREUX (Médéric RIBREUX)


Hello, bug triage...

with QGIS 2.13 on Debian, there is no conflict: p.get_storage() returns 0.

I am closing this bug.


  • status_id was changed from Open to Closed
  • resolution was changed from to fixed/implemented

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins labels May 24, 2019
@qgib qgib added this to the Future Release - Lower Priority milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins
Projects
None yet
Development

No branches or pull requests

1 participant