| 1 |
On Wed, Dec 14, 2011 at 2:55 PM, Michael Cordingley |
| 2 |
<michael.cordingley@×××××.com> wrote: |
| 3 |
> Hi there, |
| 4 |
> |
| 5 |
> I'm trying to create an ebuild for a package that isn't yet in |
| 6 |
> Portage. QuantLib-0.9.6 is currently in, but no bindings for it in |
| 7 |
> any other languages are yet there, so I thought I'd try to write up an |
| 8 |
> ebuild for the python bindings. So far, the ebuild works, right up to |
| 9 |
> the compile stage. It fails there, and I can't figure out why. |
| 10 |
> |
| 11 |
> The output of the ebuild command can be found here: http://pastebin.com/a4Cx2AYi |
| 12 |
> The current version of the ebuild is here: http://pastebin.com/PB0f1uSf |
| 13 |
> |
| 14 |
> The package that it downloads is a package of SWIG bindings for |
| 15 |
> several different languages. Doing the normal ./configure && make && |
| 16 |
> make install would try to build and install all of the bindings. I'm |
| 17 |
> trying to do ./configure && make -C Python && make install to build |
| 18 |
> only the python bindings. The idea is one package per set of |
| 19 |
> bindings. Any help would be much appreciated. Thanks! |
| 20 |
> |
| 21 |
|
| 22 |
Hi there, |
| 23 |
|
| 24 |
Might I suggest taking a look at another ebuild that builds swig |
| 25 |
bindings for an example? Please take a look at |
| 26 |
dev-libs/xapian-bindings, it sounds quite similar to what you may |
| 27 |
need. As far as one package per binding, I think that its better |
| 28 |
handled from within a single package, controlled by use flags to |
| 29 |
enable the various desired bindings. Mainly this will ease maintenance |
| 30 |
of the package down the line. The ebuild |
| 31 |
dev-libs/xapian-bindings-1.2.8.ebuild in particular is a great |
| 32 |
example. |
| 33 |
|
| 34 |
HTH, |
| 35 |
Matthew |
| 36 |
|
| 37 |
-- |
| 38 |
Matthew W. Summers |
| 39 |
Gentoo Foundation Inc. |
Archives