At 2026-01-28T00:03:49+0100, Bruno Haible via GNU roff typesetting system discussion wrote: > Deri wrote: > > > - If it contains data that may be deleted and is persisted only > > > to provide a speedup, it should be $HOME/.cache/<program>/ (or > > > $XDG_CACHE_HOME/<program>/ if that environment variable is set > > > [1]). [...] > > I think this is the appropriate place, _Inline contains a .so > > containing the C routine which improves performance with large > > fonts. If it is deleted it is recreated the next time gropdf is run. > > I will work out how to make it happen. > > Thanks. I agree that the proper location is under $HOME/.cache/gropdf/ > then. > > You will probably also need to include the architecture (ABI) in the > file name, since the user may have the same $HOME directory in > different machines with different architectures (e.g. x86_64 and > arm64, or even x86_64 and x86).
I believe it's already structured that way:
$ find ~/_Inline/ -type f
/home/branden/_Inline/config-x86_64-linux-gnu-thread-multi-5.032001
/home/branden/_Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.inl
/home/branden/_Inline/lib/auto/gropdf_1c9b/gropdf_1c9b.so
/home/branden/_Inline/.lock
> Also, if different versions of groff produce shared libraries with
> different APIs, you will need to include the groff version in the file
> name, because the user may be running different groff versions at
> different times (or even at the same time).
This much is not the case. Apart from gnulib, with which many people
are familiar (and which supports no DSO configuration TTBOMK), the groff
build produces up to four libraries--libgroff, libdriver, libbib, and
libxutil--but all are static (".a" files).
Regards,
Branden
signature.asc
Description: PGP signature
