Mario Goebbels wrote: > Is there any specific reason why any application would go completely haywire > by replacing the system Freetype with a custom one? Reason for doing this > would be enabling the "patented" TrueType byte code interpreter. > > In my case, it's specifically WINE, where it complains about an internal app > crash and stops certain Windows applications from working. Doing "pkg fix > SUNWfreetype2" immediately fixes this. The rest of the system and all native > applications continue to work peachy with any version. > > Is Freetype built differently for Indiana?
Indiana & Nevada use the same FreeType build, but it does have an additional API over the upstream FreeType, that allows enabling or disabling the bytecode interpreter at runtime instead of compile time, via the GNOME Font preferences panel - if you replaced the system FreeType, I'd expect applications using the GNOME library stack to crash from missing symbols. If you added your own freetype, I'd expect crashes if any process ever loads both the system and your FreeType into the same address space and they then get confused about which set of functions and variables to use and cross-call between each other. You can see our FreeType patches & build options at: http://src.opensolaris.org/source/xref/fox/fox-gate/XW_NV/open-src/lib/freetype/ -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
