#1130571 libowfat-dev: package does not offer supporting pkg-config file

Package:
libowfat-dev
Source:
libowfat-dev
Description:
Reimplementation of libdjb, development files
Submitter:
Brandon Richardson
Date:
2026-04-21 13:15:02 UTC
Severity:
normal
#1130571#5
Date:
2026-03-13 08:29:19 UTC
From:
To:
Dear Maintainer,

Package libowfat-dev does not offer a pkg-config file. When building
projects that depend on libowfat, finding include dirs and library
versions in build scripts is rather difficult to handle across
different platforms, and a pkg-config file would simplify this greatly.

I'm in the process of reworking opentracker to build with CMake. Linking
to libowfat-dev was quite a headache -- the include dirs are not
consistent across platforms, and the version string can only be
retrieved by parsing the changelog. The version string is needed to
enable certain build definitions depending on the available libowfat
version.

You can find the build script below which is annotated with a handful of
comments documenting the pains.

https://github.com/brandon1024/opentracker/blob/cmake/cmake/FindLibowfat.cmake

A pkg-config would allow me to more easily find and link to libowfat and
configure the build appropriately.

This wishlist bug also applies to the versions in testing and sid.

#1130571#10
Date:
2026-04-21 10:38:48 UTC
From:
To:
Hello Brandon,

Agreed. Can you write such a pkg-config file and send it here?

I read your code and was a bit surprised by the following:

	# Try to find the include dir for headers. In some environments (notably,
	# Debian), header files are dumped into /usr/include, while in others (Fedora)
	# they are in /usr/include/libowfat.
	#
	# CAS.h and windoze.h are chosen for their unique names, but they aren't
	# present in old versions of the library, so also look for a few others.
	find_path(Libowfat_INCLUDE_DIR NAMES CAS.h windoze.h openreadclose.h safemult.h PATH_SUFFIXES libowfat)

In Debian I do see the files are shipped in /usr/include/libowfat/ and
not dumped in /usr/include/ [1] as is stated. Can you explain where this
is coming from?

[1] https://packages.debian.org/sid/amd64/libowfat-dev/filelist

Thanks,

Agathe.

#1130571#15
Date:
2026-04-21 13:12:04 UTC
From:
To:
Hey Agathe,

Thanks for the response.

Of course. I'll put one together and I'll get back to you.

I was originally targeting bookworm when I first put together these build
scripts. I just took a look to confirm and the includes were indeed installed
in /usr/include in the version of libowfat-dev (0.32-4) packaged in bookworm.

https://packages.debian.org/bookworm/amd64/libowfat-dev/filelist

It looks like this was fixed in trixie (0.32-5). Good eye and good
tip, I'll have to update the bit script to reflect this.

Brandon Richardson