On Mon, Jul 6, 2009 at 10:12 AM, Adam Langley<[email protected]> wrote: > > On Mon, Jul 6, 2009 at 9:52 AM, Paweł Hajdan Jr.<[email protected]> > wrote: >> I'm investigating this mysterious fontconfig issue >> (http://crbug.com/9245), and I think it'll be useful to dig into >> fontconfig code. I plan to checkout fontconfig locally, and then >> compile Chrome against that copy. How do I do the last step? > > We use pkg-config to find fontconfig. So you should be able to build > fontconfig with > ./configure --prefix=/home/me/local > > (maybe mkdir /home/me/local first) > > then make && make install. In /home/me/local somewhere should be a .pc > file. You can export PKG_CONFIG_PATH=/home/me/local/lib/pkgconfig and > re-run GYP. (Assuming that the .pc file ended up in > .../lib/pkgconfig).
And another way to double-check this is working at this step, pkg-config --cflags --libs fontconfig should output flags mentioning your private path. > Before running the binary, you'll need to export > LD_LIBRARY_PATH=/home/me/local/lib. Try ldd ./out/Debug/chrome and > check the correct fontconfig.so is getting picked up. > > > AGL > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
