FS#65877 - [fontforge] 20200314-1 does not have include files
Attached to Project:
Arch Linux
Opened by Akos Somfai (akossomfai) - Wednesday, 18 March 2020, 08:42 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 18 March 2020, 22:03 GMT
Opened by Akos Somfai (akossomfai) - Wednesday, 18 March 2020, 08:42 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 18 March 2020, 22:03 GMT
|
Details
Description:
fontforge 20200314-1 does not have the files under /usr/include/fontforge; the previous version (20190801-2) had them. ## fontforge 20200314-1 ## [root@somi-laptop /]# pacman -Ss fontforge extra/fontforge 20200314-1 [installed] Outline and bitmap font editor [root@somi-laptop /]# ls -l /usr/include/fontforge ls: cannot access '/usr/include/fontforge': No such file or directory [root@somi-laptop /]# ## fontforge 20190801-2 ## [somi@somi-laptop ~]$ sudo pacman -Ss fontforge [sudo] password for somi: extra/fontforge 20190801-2 [installed] Outline and bitmap font editor [somi@somi-laptop ~]$ ls -l /usr/include/fontforge/ | head total 668 -rw-r--r-- 1 root root 4514 Nov 4 20:31 autowidth2.h -rw-r--r-- 1 root root 2653 Nov 4 20:31 autowidth.h -rw-r--r-- 1 root root 16786 Nov 4 20:31 baseviews.h -rw-r--r-- 1 root root 3940 Nov 4 20:31 basics.h -rw-r--r-- 1 root root 369 Nov 4 20:31 bezctx_ff.h -rw-r--r-- 1 root root 2031 Nov 4 20:31 bitmapcontrol.h -rw-r--r-- 1 root root 366 Nov 4 20:31 carbon.h -rw-r--r-- 1 root root 4671 Nov 4 20:31 chardata.h -rw-r--r-- 1 root root 3424 Nov 4 20:31 charset.h [somi@somi-laptop ~]$ sudo pacman -Qo /usr/include/fontforge/autowidth2.h /usr/include/fontforge/autowidth2.h is owned by fontforge 20190801-2 [somi@somi-laptop ~]$ |
This task depends upon
- There's FONTFORGE_INST_HEADERS defined in fontforge/CMakeLists.txt which includes autowidth.h, bitmapcontrol.h, etc. But it's apparently never used for installation.
- In inc/CMakeLists.txt there's also nothing for installing basics.h, carbon.h, etc.
Could you please report this upstream?
"The only major exclusion compared to autotools is it does not install headers and pkgconfig details. While it is certainly possible to mimic the old behaviour, I'm not seeing much reason to make libfontforge something that can be developed against. As seen in #3823, FontForge isn't well designed to be used in external projects, and we provide no stability guarantees over what is effectively internal interfaces. I doubt that we even export all required headers at the moment."
So it looks to be intentional in the upstream.
Thanks Gaetan for checking it also. Ticket can be closed.