Working perfectly now !
those amalgamations are pretty convenient imo, i don’t get why you got so much hostility on the freetype dev list
Working perfectly now !
those amalgamations are pretty convenient imo, i don’t get why you got so much hostility on the freetype dev list
Sometimes programmers can be very resistant to change. Another thing to consider is that after laboring to write code that conforms to the FreeType standards, along with comments and such, probably some might take it personally if all the sources are run through a tool that combines everything into one large glop.
The FreeType Amalgamation has been updated to version 2.4.10. It is available in the “develop” branch of the amalgamation repository. In a week if there are no reported problems it will be merged to master.
Please open an Issue on Github if you have a problem with the amalgamation. Thanks!
Hi everyone,
I just downloaded FreeTypeAmalgam.h and FreeTypeAmalgam.c, added to my project, and tried to compile it. FreeTypeAmalgam compiles successfully but when trying to execute my app (have not yet used FreeType library, only added to the app) I have two linking errors:
error LNK2001: unresolved external symbol _z_verbose
error LNK2019: unresolved external symbol _z_error referenced in function _inflate_codes
it seems that z_verbose and z_error are both external variables
I am using VS 2010 32-bit, under Windows 7.
Any help?
Thanx
How can FreeType be used in the context of JUCE? A link to a howto or a tutorial or just a little explanation would be very much appreciated.
you need FreeTypeFaces, which is in VFLib. This post talks about it although it’s a little out of date:
[quote]Hi everyone,
I just downloaded FreeTypeAmalgam.h and FreeTypeAmalgam.c, added to my project, and tried to compile it. FreeTypeAmalgam compiles successfully but when trying to execute my app (have not yet used FreeType library, only added to the app) I have two linking errors:
error LNK2001: unresolved external symbol _z_verbose
error LNK2019: unresolved external symbol _z_error referenced in function _inflate_codes
it seems that z_verbose and z_error are both external variables
I am using VS 2010 32-bit, under Windows 7.
Any help?
Thanx[/quote]
I had to uncomment these lines to get rid of that error :
#define FT_CONFIG_OPTION_USE_LZW
#define FT_CONFIG_OPTION_USE_ZLIB
Hello TheVinn !
I’m trying the implementation of FreeType in VFLib right now, and everything is working so far, I think it’s interesting to say it sometimes :mrgreen: And I think I’m going to use it in my next projects.
I have a few questions about it. I have not looked into the code that much right now, so sorry in advance if my questions are dumb
I’m developing the GUI of a plug-in with JUCE and VFLib, and I’m trying to get something as close as possible of the rendering in a PSD file, with only text and flat colours. I have seen that the functions you provide to access to the FreeType code are very limited (but highly efficient), and allow only to personnalize the rendering with the activation or not of the hinting. So, do you think it would be possible to change the way the fonts are rendered like it is in Photoshop CS4 (the parameters “Sharp”, “Crisp”, “Smooth” etc.), using code which has been developed yet in FreeType ? Or maybe that would need to develop new code ?
Does using VFLib+FreeType allow the text rendering with JUCE to be EXACTLY the same if the application is compiled on both Windows and Mac OS X ? It was an issue for me before (I can’t say I prefer the native rendering of Mac OS X or the one of JUCE+Windows applications, but I really HATED to see that Inspiration does not look the same on each OS, and that I can’t do anything about it…)
What do you think of the speed of the rendering with VFLib+FreeType compared with the text rendering of JUCE ?
Thanks a lot for the answers, and for having developed+shared that
This depends on what FreeType offers. I am not very familiar with the FreeType API, perhaps there are some routines that can be used to adjust the production of outlines? I think that Photoshop is applying some operation to the curves themselves and not the actual rendered pixels (or else letters wouldn’t look right).
Yes, you should get exactly the same result as long as the font is the same.
Mostly the same. I use the software renderer in JUCE, it’s always faster than the other choices.
You’re welcome! I’m glad to hear it is useful.
Thanks for the answers