1- What compiler(s) would you say FreeType is compatible with? We
are flexible enough to change compilers.
FreeType is written in ANSI C, so basically all compilers should work.
The problem is with compilers which are less than ANSI C...
2- Aside from scaling fonts at run time, what
Are you willing to do the work to make sure no FreeType contributor
currently has a patent on code they have contributed?
This should be doable, given that there are just a handful of
contributors who added longer, non-trivial stuff.
Werner
Hello,
Just to make it clear, I'm too in favor of adding an Apache2-like patent
clause to the license.
And for the sake of full-disclosure, my employer does releases quite a
large amount http://source.android.com of Apache-2 licensed code.
On Fri, Jan 13, 2012 at 8:34 PM, Eric Rannaud
On 17 January 2012 09:25, David Turner di...@google.com wrote:
An easier approach would be to ask for all future contributions to be
covered by FreeType License 1.1,
...
Apache2 is not compatible with GPLv2 notably because of this
particular patent clause (that's the general agreement anyway
On Tue, Jan 17, 2012 at 3:53 PM, Dave Crossland d...@lab6.com wrote:
But its GPLv2 only :-(
Apache 2 is GPLv3 compatible.
So I'd suggest either using Apache 2, or using FreeType License 1.1
and GPLv2-or-later.
Apache 2 or GPLv2-or-later have the same problems: they require changing
the
Hi,
after I submitted my first patches I found a bunch of other PIC issues. I
see that you have fixed some of the same things I found too, mostly
missing includes to the various error-headerfiles, and a bunch of
unitialized variables for clazz and the various PIC modules, and pointer
Dear Erik,
Of course, I want to receive the patch to improve (rather,
I should call restore) PIC build. I wish if my overhaul
have not made you troubled.
Erik Dahlstrom wrote:
diff --git a/modules/libfreetype/include/freetype/internal/ftdriver.h
