Fonts are looking ugly even if antialiasing is ON. I know that the reason is: bytecode interpreter at freetype2 package is OFF by default. All that is because of patent issues, I've read it. But if I live at country where their patents are not valid, I'd like to have a possibility to switch it ON when compile. Or may be this possibility is not documented?
root@vapier 0 freetype # emerge freetype -pv These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-libs/freetype-2.1.4-r1 -doc +zlib -bindist root@vapier 0 freetype # grep bindist /usr/portage/profiles/use.desc bindist - Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues)
Sorry, may be I do not get the idea: I do not use pre-built packages at all, and just want to compile the library _using_ bytecode interpreter at freetype2. Is it ON by default when compiled on my computer? I tried and it seemed to me that rather not. Am I wrong? P.S. I saw KDE with freetype2 bytecode interpreter ON and OFF on friend's Mandrake9.1 distro (it is ON when freetype2 rpm is installed from PLF). The difference is _obvious_ for 'arial', 'verdana' and 'sans' fonts, especilally when antialiasing is OFF.
In other words: Is it possible to check, whether the bytecode interpreter is ON? Thanks in advace and forgive me if I'm just stupid and annoy you.
look to see if you 'bindist' in /var/db/pkg/media-libs/freetype-*/USE if you dont, `env USE=bindist emerge freetype`
Thanks for your valuable help and assistance, I undersood the idea. The bug can be closed.
*** Bug 87121 has been marked as a duplicate of this bug. ***
unfortunately even when I apply the resolution to this bug "USE=bindist emerge freetype" there is still a ewarning saying bytecode has NOT been sucessfull. to emerge with bytecode use my attachment at bug 87121
