FS#63925 - liblo package does not include libloConfig.cmake file

Attached to Project: Community Packages
Opened by Claudio Cabral (claudiocabral) - Thursday, 26 September 2019, 15:03 GMT
Last edited by David Runge (dvzrv) - Friday, 27 September 2019, 08:17 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The current PKGBUILD uses make to generate and install all the files.
This does not include libloConfig.cmake, generated only when using cmake.

package information:
Name : liblo
Version : 1:0.30-2
Description : A lightweight OSC (Open Sound Control) implementation
Architecture : x86_64
URL : http://liblo.sourceforge.net/
Licenses : LGPL2.1
Groups : None
Provides : liblo.so=7-64
Depends On : glibc
Optional Deps : None
Required By : ardour xjadeo zam-plugins
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 2.02 MiB
Packager : David Runge <dave@sleepmap.de>
Build Date : Wed 07 Aug 2019 09:08:29 PM CEST
Install Date : Sun 18 Aug 2019 05:19:12 PM CEST
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 27 September 2019, 08:17 GMT
Reason for closing:  Won't fix
Additional comments about closing:  liblo is build with the default build system, not cmake
Comment by Eli Schwartz (eschwartz) - Friday, 27 September 2019, 06:16 GMT
The cmake build is non-default, hidden away in a subdirectory, contains code to extensively parse configure.ac for various metadata (e.g. library versioning) and the project already installs a cross-build-system pkg-config file. Why do you need to look for it with cmake? Why not use the standard pkg-config?
Comment by David Runge (dvzrv) - Friday, 27 September 2019, 08:17 GMT
@claudiocabral: To my knowledge upstream only ever accepted cmake as being the non-default solution (for Windows).
As cmake can make use of /usr/lib/pkgconfig/liblo.pc to find liblo and https://github.com/radarsat1/liblo/blob/master/cmake/libloConfig.cmake.in is a templated file that will not be generated, if not building with cmake, I will close this.

Loading...