Apologies for the late response. You can find the pkg-config file
below (trixie). The version string will need to be adjusted if
targeted for forky or sid.
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include/libowfat
Name: libowfat
Description: Reimplementation of libdjb
Version: 0.34-2
Libs: -L${libdir}
Cflags: -I${includedir}
On Tue, Apr 21, 2026 at 3:12 PM Brandon Richardson
<[email protected]> wrote:
>
> Hey Agathe,
>
> Thanks for the response.
>
> > Agreed. Can you write such a pkg-config file and send it here?
>
> Of course. I'll put one together and I'll get back to you.
>
> > 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?
>
> 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
>
> On Tue, Apr 21, 2026 at 12:38 PM Agathe Porte <[email protected]> wrote:
> >
> > Hello Brandon,
> >
> > > 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.
> >
> > Agreed. Can you write such a pkg-config file and send it here?
> >
> > > 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.
> >
> > 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.
