Mercurial > pub > dyncall > bindings
comparison ruby/rbdc/README.txt @ 10:6493c9ed4b33
- ruby and python binding readme updates
author | cslag |
---|---|
date | Sat, 26 Mar 2016 01:10:22 +0100 |
parents | 80273969f043 |
children | 739c40f35a6a |
comparison
equal
deleted
inserted
replaced
9:8a45a05ff64e | 10:6493c9ed4b33 |
---|---|
1 dyncall ruby bindings | 1 dyncall ruby bindings |
2 Copyright 2007-2015 Tassilo Philipp | 2 Copyright 2007-2016 Tassilo Philipp |
3 | 3 |
4 | 4 |
5 BUILD/INSTALLATION | 5 BUILD/INSTALLATION |
6 ------------------ | 6 ------------------ |
7 | 7 |
8 1) The extension isn't built here, but its code along with dyncall's source is bundled | 8 1) The extension isn't built here, but its code along with dyncall's source is bundled |
9 in a .gem file to then be built and installed on the platform where the gem is installed. | 9 in a .gem file to then be built and installed on the target platform. |
10 So, you need dyncall's full source code to be included. Unfortunately, the .gemspec isn't | 10 So, you need dyncall's full source code to be included. Unfortunately, the .gemspec isn't |
11 flexible enough to pull from different paths, so building the .gem file requires dyncall | 11 flexible enough to pull from different paths, so building the .gem file requires dyncall |
12 to be found next to rbdc.c and extconf.rb. This means either copy dyncall's base directory | 12 to be found next to rbdc.c and extconf.rb. This means either copy dyncall's base directory |
13 do ./dyncall or create a symlink ./dyncall, that points to it. | 13 do ./dyncall or create a symlink ./dyncall, that points to it. |
14 | 14 |