Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Alexei Podtelezhnikov
How about a shared header file if those modules share a structure? Don't you see that this patch set is just a pile of pure stinking crap??? On Tue, Feb 21, 2012 at 9:56 AM, Vinnie thev...@yahoo.com wrote: Werner: 2012-02-20  Vinnie Falco vinnie.fa...@gmail.com   ftgrays.c, ftraster.c:

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Collyer, Oliver, SI
Unless I've misunderstood, It seems to me that the changes being made are not to amalgamate FreeType into a couple of files, but just to rename some stuff/change some #defines to make this possible for another tool to optionally do. If so, I really can't see what the problem is and why you're

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Vinnie
Date: Tue, 21 Feb 2012 08:02:43 -0500 From: Alexei Podtelezhnikov apodt...@gmail.com You planing this for Stone Age people who do not know how to use make. I rest my case. Actually, that is true. My target audience includes musicians or artists who are beginning to dabble in C / C++

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Dmitry Timoshkov
Vinnie thev...@yahoo.com wrote: With an amalgamated version of FreeType I can add support for hinted fonts to my open source offerings, while including the entire FreeType distribution as a single source file instead of a large tree. How about providing a single precompiled library file for

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Alan Coopersmith
On 02/21/12 05:02 AM, Alexei Podtelezhnikov wrote: All this work is from Stone Age, when noone shared and everyone only used a single file and a single command to build something. Using anything but a shared library for FreeType just seems to be begging for pain everytime FreeType has to issue

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Dmitry Timoshkov
Vinnie thev...@yahoo.com wrote: How about providing a single precompiled library file for these people? That would only work for one particular build environment, and within that environment, only one target. For example, debug, or release. Or 32 bit versus 64 bit. If the resulting

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Alexei Podtelezhnikov
On Tue, Feb 21, 2012 at 10:44 AM, Vinnie thev...@yahoo.com wrote: Date: Tue, 21 Feb 2012 08:02:43 -0500 From: Alexei Podtelezhnikov apodt...@gmail.com You planing this for Stone Age people who do not know how to use make. I rest my case. Actually, that is true. My target audience

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Alexei Podtelezhnikov
On Tue, Feb 21, 2012 at 11:03 AM, Chris Morgan chmor...@gmail.com wrote: Hey. This kind of response isn't cool man. If Vinnie's patches disambiguate and otherwise clarify the code then they are good changes, even if it enables him to do things that we find odd. There is nothing ambiguous in

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Vinnie
From: Alexei Podtelezhnikov apodt...@gmail.com Sent: Tuesday, February 21, 2012 8:28 AM It is hard to believe that there are people who'll dive into font rendering without first learning how to use multiple files and libraries in a project. I agree, it is hard to believe but that's just

Re: [ft-devel] FreeType patches to support amalgamation

2012-02-21 Thread Alexei Podtelezhnikov
On Tue, Feb 21, 2012 at 11:54 AM, Vinnie thev...@yahoo.com wrote: From: Alexei Podtelezhnikov apodt...@gmail.com Sent: Tuesday, February 21, 2012 8:28 AM It is hard to believe that there are people who'll dive into font rendering without first learning how to use multiple files and