[GRASS-dev] [GRASS GIS] #2448: Fontconfig error with cairo on Windows

Helmut Kudrnovsky hellik at web.de
Fri Sep 11 00:28:16 PDT 2015

Paul Kelly wrote
>> a feasable way may be:
>> - another flag e.g. to write fontcap file to %APPDATA%GRASS7 where
>> already
>> the addons are stored
>> - all the modules which are working with fonts seems to search for the
>> fontcap file in $GISBASE/etc; adding a second search path (e.g.
>> %APPDATA%GRASS7) to these modules if the file is not available in
>> $GISBASE/etc
> Similar to this, I was just going to suggest why don't you set the 
> GRASS_FONT_CAP environment variable to a path that *is* writable. Then 
> g.mkfontcap, and all the modules that use the fontcap, will simply use 
> that instead of the fontcap in $GISBASE/etc. This mechanism is explicitly 
> designed for the situation where a user doesn't have write access to 
> $GIBASE/etc and needs to override the system fontcap file.
> However, I don't think this is a good solution if the installation is 
> required to be available to other users on the same Windows machine as the 
> writable path will likely only be available to that user, if I understand 
> correctly.
> Paul


I wasn't aware of GRASS_FONT_CAP environment variable. [1]

    [g.mkfontcap, d.font, display drivers]
    specifies an alternative location (to $GISBASE/etc/fontcap) for the font
configuration file.

using this variable may ease a lot this issue.

in Windows there is C:\Users\All Users availabe, where application stores
files etc which should be available for all users.

[1] https://grass.osgeo.org/grass70/manuals/variables.html

best regards
View this message in context: http://osgeo-org.1560.x6.nabble.com/Re-GRASS-GIS-2448-Fontconfig-error-with-cairo-on-Windows-tp5221935p5223702.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

More information about the grass-dev mailing list