Mercurial > pub > dyncall > bindings
changeset 10:6493c9ed4b33
- ruby and python binding readme updates
| author | cslag |
|---|---|
| date | Sat, 26 Mar 2016 01:10:22 +0100 |
| parents | 8a45a05ff64e |
| children | 8070dae59227 |
| files | python/pydc/README.txt ruby/rbdc/README.txt |
| diffstat | 2 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/python/pydc/README.txt Sat Mar 26 01:09:51 2016 +0100 +++ b/python/pydc/README.txt Sat Mar 26 01:10:22 2016 +0100 @@ -10,7 +10,7 @@ 1) make sure dyncall is built and libraries/headers are in include paths or CFLAGS points to them, etc. -2) Build and install this gem with: +2) Build and install this extension with: python setup.py install
--- a/ruby/rbdc/README.txt Sat Mar 26 01:09:51 2016 +0100 +++ b/ruby/rbdc/README.txt Sat Mar 26 01:10:22 2016 +0100 @@ -1,12 +1,12 @@ dyncall ruby bindings -Copyright 2007-2015 Tassilo Philipp +Copyright 2007-2016 Tassilo Philipp BUILD/INSTALLATION ------------------ 1) The extension isn't built here, but its code along with dyncall's source is bundled - in a .gem file to then be built and installed on the platform where the gem is installed. + in a .gem file to then be built and installed on the target platform. So, you need dyncall's full source code to be included. Unfortunately, the .gemspec isn't flexible enough to pull from different paths, so building the .gem file requires dyncall to be found next to rbdc.c and extconf.rb. This means either copy dyncall's base directory