2018-05-09 17:21 GMT+02:00 Fis Trivial <ybbs.da...@hotmail.com>: > > 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. During the build process, One would first build the c++ part by > cmake, then chdir into each language binding sub-directory and invoke > its build system. > > For packaging them in guix, one way to deal with it is building each > binding as an independent package, each package has it's own > dependencies for the specific binding and common dependencies for C++ > part, that way, we will have N independent packages, for N language > binding. But it will result in a huge waste of computing resource. I > don't want to waste precious computing time of guix's build farm. >
Maybe I'm being naive, but I don't understand why this would involve any further overhead You could have the c++ part as a dinamically linked library and the bindings would have it as a dependency What's the overhead in this ?
