1 |
Let's change USE=libffi to more generic USE=ffi so it will cover also |
2 |
eg. ffcall. DESCRIPTION could be simple: |
3 |
|
4 |
"Enable support for Foreign Function Interface" |
5 |
|
6 |
-- cut -- |
7 |
|
8 |
1. "libffi" (dev-java/jamvm): use dev-libs/libffi to call native methods |
9 |
|
10 |
2. "libffi" (dev-python/pygobject): Enable support to connect to signals |
11 |
on python objects from C. |
12 |
|
13 |
3. "libffi" (gnustep-base/gnustep-base): Use dev-libs/libffi instead of |
14 |
dev-libs/ffcall |
15 |
|
16 |
4. "libffi" (sys-devel/gcc): Build the portable foreign function |
17 |
interface library |
18 |
|
19 |
5. "libffi" (sys-devel/llvm): Add support to call arbitrary external |
20 |
(natively compiled) functions via dev-libs/libffi |
21 |
|
22 |
6. "ffi" (app-i18n/uim): Enable support for virtual/libffi |
23 |
|
24 |
7. "ffi" (dev-ruby/nokogiri): Use the Foreign Function Interface library |
25 |
(as provided by dev-java/jruby or dev-ruby/ffi depending on the |
26 |
implementation) rather than building a C extension to wrap around the |
27 |
libxml/libxslt interfaces. Note: JRuby always uses the FFI interface as |
28 |
native extensions are not supported. |
29 |
|
30 |
--- cut --- |
31 |
|
32 |
Any objections... ? |