On Tue, Aug 28, 2012 at 1:17 PM, Helmut Tessarek <ml@xxxxxxxxxxx> wrote: > Well, ffmpeg calls the fontconfig functions so it has the same environment. > > Even, if a sub-process was spawned or a thread created it would still have the > same environment. But this is not the case. FFmpeg is just calling fontconfig > functions. Thus setting an env var in ffmpeg should get picked up by the > fontconfig lib. And this is exactly my point. I have no idea why it does not > get picked up. Other than that, those setenv thing has to be called before FcInit(). if it's written in C++ say and FcInit() is called in any constructors, it may not work as expected unless you are sure you did it before calling FcInit(). -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig