On Tuesday, 26 February 2019 11:38 Simon Lees wrote:
On 26/02/2019 20:59, Michal Kubecek wrote:
On Tuesday, 26 February 2019 11:01 Axel Braun wrote:
Hi,
I'm currently trying to build the orthanc-postgresql package.
Problem is that most Orthanc plugins re-use a part of the C++ code of Orthanc, independently of the development headers.
To solve this issue, we can put the source code distribution "Orthanc-1.5.5.tar.gz" file into a folder called "ThirdPartyDownloads" located next to the "PostgreSQL/CMakeLists.txt" file.
Providing the source package is IMO not the smartest idea, as this requires maintenance of version for orthanc not only in hte orthanc package, but as well in each plugin package
Can I somehow include the orthanc.src.rpm in the build for the plugin?> How about building it as a subpackage of orthanc?
Michal Kubecek
Yeah normally you'd create an orthanc-devel which contains all the header files installed into /usr/include/, in a normal case the header files plus any associated shared libraries in /usr/lib64 should be enough to build plugins. But this approach makes the assumption that the upstream build system works in a sane and normal way which isn't always the case. Sometimes its quicker to fix the upstream build files so that cmake will look for the preinstalled version fo the source code and libs rather then one in the directory next to it.
What I meant was - add the plugin tarball as additional source to orthanc package - unpack it into a separate directory in prepare phase - build it after the build of the main directory - package the plugin files into a subpackage There are already some packages which work like this but I can't provide an example from the top of my head. Michal Kubecek -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org