Yes. So far there are 6 sets of changes, using the naming
conventions that you recommended. These patches were created off an
unmodified copy of the publicly available FreeType
2.4.8. Unfortunately I'm using SVN but the patches should still be
applicable (?)
Thanks for the patches! I've
One more minor set of changes, I moved an inline comment to the
previous line on a couple of #include lines.
What is this change set good for, except cosmetics?
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
Hi,
For first, I state that I have no objection against the decision by
Werner, because now the time he spends for the maintenance of FreeType2
(in official branch) is longer than those of other FreeType2 developers
(maybe except of David Turner).
But, if I just talk about the idea to change
Alan Coopersmith wrote:
Using anything but a shared library for FreeType just seems to be begging
for pain [...]
Unlike many high-profile packages, Freetype is also used on (mostly
embedded) platforms where shared libraries just do not exist.
Also if some vendor has a design which, perhaps for
Putting the prefix or postfix to all names, we can avoid the
conflicts, but it makes the names longer, and it makes the sources
eye-unfriendly (especially for the die-hard VT100 emulator users
like me).
I usually strictly enforce a 78 character per line limit, so I also
want to avoid overly
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:
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
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++
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
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
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
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
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
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
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
To be honest, I am perplexed by this amalgamation exercise.
All of this apparently needed because some obscure in-house
tool does not know how to resolve the name conflicts.
Teach the damn tool how to resolve the name conflicts
by adding prefixes or suffixes!
Why do you butcher perfectly legal
You again manage to present this as a legitimate goal :)
It is your tool that breaks the code :) You are not fooling me here.
Again, I'll say that this is just such a bizarre objective that
you HAVE TO justify this and tell which platform on Earth
needs it. Remember it has to be a platform which
To be honest, I am perplexed by this amalgamation exercise. All of
this apparently needed because some obscure in-house tool does
not know how to resolve the name conflicts.
I don't think so.
Teach the damn tool how to resolve the name conflicts by adding
prefixes or suffixes! ...
Again, I'll say that this is just such a bizarre objective that you
HAVE TO justify this and tell which platform on Earth needs it.
??? It's not related to a specific platform at all. It's a matter of
an easy way to distribute the FreeType code with a very few number of
files.
Remember it
On Mon, Feb 20, 2012 at 5:45 PM, Werner LEMBERG w...@gnu.org wrote:
Again, I'll say that this is just such a bizarre objective that you
HAVE TO justify this and tell which platform on Earth needs it.
??? It's not related to a specific platform at all. It's a matter of
an easy way to
20 matches
Mail list logo
