Menu

#588 installing CBM fonts goes wrong

v2.4.x
closed-out-of-date
None
Linux
Buildsystem
2019-01-20
2014-12-07
gpz
No

something with the font installation goes wrong... after doing "sudo make install" (which needs to be done because else a lot of files can not be written) the fonts end up in /usr/games/lib64/vice/fonts/ (which is correct for the install prefix i am using) and /root/.fonts (which is certainly totally wrong!). only after manually copying the fonts to my users homedir (cp /usr/games/lib64/vice/fonts/* ~/.fonts/) everything works as expected.

two questions arise here... first, why doesnt it find the fonts installed to /usr/... - and why would it try to install fonts to my users directory? what if vice is installed by the root user for system wide use? noone will have working fonts except the root user? this seems very broken, there must be a better way to do this :)

Discussion

  • Greg King

    Greg King - 2014-12-12

    The "data/fonts/Makefile.am" file is old and primitive. It has things that should be in "Makefile.in". And, it suffers from a misunderstanding about where the fonts belong. They don't belong to VICE; they're donated to the X Window System. They must be installed where the X server looks for fonts. That "~/.fonts/" stuff is a clumsy workaround for the misunderstanding.

    I have attached a patch that fixes most of the bugs. But, I used a hard-wired path to a font directory because I don't know an easy way to learn what a host's current X System path is.

     
    • Greg King

      Greg King - 2014-12-14

      I just realized that we don't need to install both BDF and PCF versions of fonts. The X server reads only one of them.

      Therefore, this new version of Makefile.am removes the BDF font if the PCF font was created.

       
  • compyx

    compyx - 2016-10-20

    Has anyone ever tried this patch? As the build system is now, fonts are installed into ${prefix}/lib[64]/vice/fonts. Which my X server will never look in for fonts.

    Manually copying the fonts to /use/share/fonts enabled the CBM font on my box, but is something the build system should do.

    So how do we figure out where the fonts should go?

     
  • compyx

    compyx - 2019-01-20
    • status: open --> closed-out-of-date
     
  • compyx

    compyx - 2019-01-20

    This issue is now out-of-date: make install on Unix will copy the CBM.ttf file to VICEDATADIR/fonts and Gtk3 will load it dynamically via archdep code, so installing CBM.ttf in the proper place for any given OS is not required anymore. All other font files are obsolete since we only have SDL2 (uses CHARGEN) and Gtk3 (uses CBM.ttf) now.

     

Log in to post a comment.