On Mon, Aug 27, 2012 at 8:27 AM, Helmut Tessarek <ml@xxxxxxxxxxx> wrote: > Hi Raimund, > > On 26.08.12 17:50 , Raimund Steger wrote: >> No, this must resolve to an absolute path at compile time. > > What about these 2 configuration parameters: > > --with-baseconfigdir=DIR > Use DIR to store the base configuration files > [default=SYSCONFDIR/fonts] > --with-configdir=DIR Use DIR to store active configuration files > [default=BASECONFIGDIR/conf.d] > > Do they have to be absolute paths as well? Yes. >> But you can set FONTCONFIG_PATH to a non-default configuration root at >> runtime, i. e. FONTCONFIG_PATH=/path/to/binary/cfg. > > I don't want to use ENV vars, otherwise I'd have to use a wrapper script to > start the binary. > There are binaries available that search in the same or relative directory for > the font configuration files. that would be only way to go to read the configuration from _current path_ so far. if it's the fixed path for the specific application, you can use --with-baseconfigdir=/path/to/binary/cfg and put your rules on /path/to/binary/cfg/conf.d or simply use --with-configdir=/path/to/binary/cfg. Regards, -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
