-
Notifications
You must be signed in to change notification settings - Fork 165
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
Ship GEOS with the project for MRI users #272
Comments
Note on advancement, there is #291 for binding another library than geos-config, and there is https://github.com/buonomo/test-geos for downloading and installing geos in extconf.rb |
Current state:
|
I would love to see rgeo brings its own geos automatically, just like nokogiri brings its own libxml2: https://nokogiri.org/#cruby |
@eis-ioki thanks for the feedback! Do you want to contribute on that topic? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The V3 roadmap includes our goal of having an easier installation process.
Since our pure ruby implementation is incomplete, and our the FFI version is way slower than the Geos CAPI version, it is clear that we want to keep the CAPI, and make it easier to install if we can.
Some idiomatic projects (such as https://github.com/sass/sassc-ruby) are showing us a good way to operate: intregrate GEOS directly in the CAPI build. There are tons of other projects that are doing so, you can just search github for those.
Once we have a fixed version of GEOS shipped with RGeo, we also want one to be able to still be able to install its custom GEOS version.
One last thing, including GEOS version in our version, or a helper would be nice... Think
SELECT postgis_full_version()
for RGeo.I am aware that this task may be a challenge for a first contributor. However, if you want to contribute, we'll be there to work together 💪
The text was updated successfully, but these errors were encountered: