The boinc configure script has support for making packages of this type. The options --enable-pkg-client, --enable-pkg-manager, --enable-pkg-libs, --enable-pkg-devel should set things correctly to build those packages. "make stage" moves the executables and libraries into the staging directory (boinc/stage). For example if you use /usr as the prefix, then the boinc client would be moved into boinc/stage/usr/bin. From there you should be able to use your package management system to build the package, either directly or via chroot.
Eric 2009/10/26 Nicolás Alvarez <[email protected]>: > El Lunes 26 Oct 2009 16:27:51 Karol Babioch escribió: >> Hi, >> >> I'm about to build boinc from source, so I can provide packages for my >> favorite linux distribution (Arch). I plan to split the package up, >> similar to the Debian package style. I thought of the following >> packages: >> >> * boinc-client >> * boinc-server >> * boinc-manager > > I don't think you should make a server package at this stage. Gabor Gombas did > it for Debian, but to actually make a project you have to write custom > components, and to compile the custom components you need the full BOINC > source code anyway. So the package isn't very useful at the moment. It would > need changes to the code to get it properly packaged. > >> I think I have to exclude the libraries in another package, so every of >> the above packages can make use of them without the need to provide the >> libraries themselves. Otherwise I would have to compile each of the >> above package with the libraries, so they would overwrite each other as >> soon as you install one of them. Is this right, or is there a better >> solution? > > libboinc is usually linked statically, so they wouldn't "overwrite each > other". > > If you link dynamically, then of course there should be a separate package for > the library, and client/manager depending on them. But note that the ABI/API > isn't guaranteed to be stable at all, so you probably need a strict version > dependency between the packages. > >> Furthermore I'm wondering how to get the libcudart.so library, which is >> needed to make use of the gpu. I can extract this file from the linux >> installer, and adding it to my package. However I would like to compile >> this library from the source(s), so it is up to date whenever I update >> the package itself. >> >> I couldn't find any parameter for configure, so is there a way to build >> this library? Is it documented? > > libcudart is proprietary, made by NVIDIA. It would be installed as part of the > drivers. It shouldn't be packaged as part of BOINC. > > -- > Nicolas > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
