Re: Dealing with language bindings for libraries.

On 09/05/2018 20:00, Julien Lepiller wrote: We already have such a case: capstone and python-capstone. There is no redundancy since python-capstone knows how to load the shared library created in the capstone package. So we have two packages, with the same My situation is a bit different. The

Re: Dealing with language bindings for libraries.

2018-05-10 11:27 GMT+02:00 Fis Trivial : > > Catonano writes: > > > 2018-05-09 17:21 GMT+02:00 Fis Trivial : > > > >> > >> Hi, Guixs. > >> > >> Recently I encountered some libraries that's written in c++ and have > >> multiple language bindings,

Re: Dealing with language bindings for libraries.

Catonano writes: > 2018-05-09 17:21 GMT+02:00 Fis Trivial : > >> >> Hi, Guixs. >> >> Recently I encountered some libraries that's written in c++ and have >> multiple language bindings, each of them has their corresponding build >> system, namely, R, Python, Java. And all

Re: Dealing with language bindings for libraries.

2018-05-09 17:21 GMT+02:00 Fis Trivial : > > Hi, Guixs. > > Recently I encountered some libraries that's written in c++ and have > multiple language bindings, each of them has their corresponding build > system, namely, R, Python, Java. And all the bindings are in > tree.

Re: Dealing with language bindings for libraries.

Ricardo Wurmus writes: > Fis Trivial writes: > >>> We can also >>> reuse parts of build systems without having to reimplement them >>> manually. We would simply reference them with something like this: >>> >>> --8<---cut

Re: Dealing with language bindings for libraries.

Fis Trivial writes: > An ideal scenario would be the one that we can specify multiple outputs > for one packages, each output corresponds to one language binding, and > we can specify different dependencies and build system for each > output. Is there any chance we can

Re: Dealing with language bindings for libraries.

Fis Trivial writes: >> We can also >> reuse parts of build systems without having to reimplement them >> manually. We would simply reference them with something like this: >> >> --8<---cut here---start->8--- >> (add-after 'install

Re: Dealing with language bindings for libraries.

Ricardo Wurmus writes: > Fis Trivial writes: > >> An ideal scenario would be the one that we can specify multiple outputs >> for one packages, each output corresponds to one language binding, and >> we can specify different dependencies and build system for each >>

Re: Dealing with language bindings for libraries.

Le Wed, 9 May 2018 18:25:13 +0200, Konrad Hinsen a écrit : > On 09/05/2018 17:21, Fis Trivial wrote: > > > An ideal scenario would be the one that we can specify multiple > > outputs for one packages, each output corresponds to one language > > binding, and we can

Re: Dealing with language bindings for libraries.

On 09/05/2018 17:21, Fis Trivial wrote: An ideal scenario would be the one that we can specify multiple outputs for one packages, each output corresponds to one language binding, and we can specify different dependencies and build system for each output. Is there any chance we can do that in