On 2011/04/26 11:40:25, reed1 wrote: > Curious, who are the external clients of SkFontHost? It ...
13 years, 4 months ago
(2011-04-26 16:38:46 UTC)
#3
On 2011/04/26 11:40:25, reed1 wrote:
> Curious, who are the external clients of SkFontHost? It was (originally)
> intended to just be a porting layer api.
Here's a code search for references to SkFontHost in the Chrome tree that
*aren't* in the Skia tree:
http://codesearch.google.com/codesearch?hl=en&vert=chromium&lr=&q=SkFontHost+...http://codesearch.google.com/codesearch?hl=en&vert=chromium&lr=&q=SkFontHost+...
I believe it's used for the font IPC stuff we do on Linux for the sandbox. That
is, we have a SkFontHost_fontconfig implementation that calls into some
FontConfigInterface API which may potentially do IPCs to another process to get
the file handle. (I didn't write this code so my description may be wrong...)
Sorry, I needed to modify two more headers to get a full Chrome build working. ...
13 years, 4 months ago
(2011-04-26 19:44:02 UTC)
#5
Sorry, I needed to modify two more headers to get a full Chrome build working.
The additional files are SkMetaData.h and Sk64.h.
If this looks good, can you land it for me?
Issue 4436057: Tag some more API headers with SK_API so they are exposed
Created 13 years, 4 months ago by evan
Modified 13 years, 4 months ago
Reviewers: reed1, agl
Base URL: http://skia.googlecode.com/svn/trunk/
Comments: 0