![](https://seccdn.libravatar.org/avatar/e6dc8afd12f42302ae7b5ea72e4dd686.jpg?s=120&d=mm&r=g)
Martin Pluskal <martin@pluskal.org> writes:
On Tue, 2018-12-18 at 10:41 +0100, Dan Čermák wrote:
Hi list,
I would like to package a (kind-of) header only C++ library (https://github.com/emilk/loguru). The problem is, that it actually ships a cpp file in it's source tree (so I guess it needs to be compiled to a shared library?).
The issue at hand is, that loguru is designed to be embedded in your C++ project (there is *a lot* of compile time switches) and even running the test suite from a shared library requires a lot of patching of the source tree.
What would be the correct procedure for packaging? Create a shared library nevertheless? Or create multiple libraries with some common compile time switches? Or just install the sources into the file system? Hi
I guess you mean something like installing just headers like in i.e [1] - if so just having -devel subpackage is absolutely ok.
Yes, kind of. The difference is however that loguru ships a cpp file and not just headers. I would personally prefer to just ship the sources, as upstream clearly wants it that way. Cheers, Dan
Cheers
M
1. https://build.opensuse.org/package/view_file/devel:libraries:c_c++/sparsehas...
-- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)