Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Auto detect libraptor2.so.0 (for Ubuntu compatibility)
- Loading branch information
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,5 +14,4 @@ matrix: | |
| - rvm: rbx-2 | ||
| before_install: | ||
| - sudo apt-get install libraptor2-0 | ||
| cache: bundler | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -79,7 +79,7 @@ module RDF | |
| # @author [Arto Bendiken](http://github.com/bendiken) | ||
| # @author [John Fieber](http://github.com/jfieber) | ||
| module Raptor | ||
| LIBRAPTOR = ENV['RDF_RAPTOR_LIBPATH'] || ['libraptor2', 'libraptor2.so.0'] unless const_defined?(:LIBRAPTOR) | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. 
dwbutler
Author
Member
|
||
| RAPPER = ENV['RDF_RAPTOR_BINPATH'] || 'rapper' unless const_defined?(:RAPPER) | ||
|
|
||
| require 'rdf/raptor/version' | ||
|
|
||
In principle, we ought to try for
libraptor2.so.0before tryinglibraptor2.so, as the former is the actual current ABI version that we're programming for.If and when
libraptor2.so.1is eventually released, our code will continue to work 100% so long as we ask forlibraptor2.so.0(and both are installed), falling back tolibraptor2.so(which would then likely be a symlink tolibraptor2.so.1) if it's unavailable. In the latter case, we may still work 90%+ if the ABI changes are not too significant; but in terms of ordering, we certainly want the 100% compatibility over the 90%+ case, by default.