Ah yes, CMakeLists has an INSTALL_FONTS option, which you can turn off. It's not exposed to the Makefile wrapper, we can add that also if you want. (Some people use the Makefile wrapper, some directly use CMake. Either is fine.)
I wish freetype included a default font embedded into the library itself, as a fallback for misconfiguration or no system fonts being found. That would have solved all these problems for me, without desiring to bundle a fallback font myself. > On Dec 2, 2015, at 1:38 PM, Richard Shaw <[email protected]> wrote: > > On Wed, Dec 2, 2015 at 11:35 AM, Larry Gritz <[email protected] > <mailto:[email protected]>> wrote: > Is the issue the bundling, the license terms, where the files live, or just > the principle of it all? > > Bundling, but fonts can be a tricky issue although they don't look to be > installed anywhere where they would be a problem. > > I think there's already a font install option. I'll start there. > > > It will still find the system fonts just like it always did. > > The purpose of the bundled fonts it to make sure there was at least one > option wherein users (and my unit tests) could get identical results for text > rendering on all platforms, and for it to be able to make some fallback if > another requested font was not found anywhere. It is not critical to any > operation, and we can easily disable it. If it's helpful to you, I'm happy to > make a build-time option to skip it. > > It's fine to keep them in the source for testing purposes as long as I can > prevent them from being installed. > > Thanks, > Richard > -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
