What new  freetype release are going to be there?

On Tue, Apr 3, 2018 at 7:10 PM, <freetype-devel-requ...@nongnu.org> wrote:

> Send Freetype-devel mailing list submissions to
>         freetype-devel@nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.nongnu.org/mailman/listinfo/freetype-devel
> or, via email, send a message with subject or body 'help' to
>         freetype-devel-requ...@nongnu.org
>
> You can reach the person managing the list at
>         freetype-devel-ow...@nongnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freetype-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Time for a new FreeType release (Nikolaus Waxweiler)
>    2. Re: Time for a new FreeType release (Nikolaus Waxweiler)
>    3. Re: Time for a new FreeType release (Nikolaus Waxweiler)
>    4. Re: Time for a new FreeType release (Vincent Torri)
>    5. Re: Time for a new FreeType release (Vincent Torri)
>    6. Re: Time for a new FreeType release (Nikolaus Waxweiler)
>    7. Re: Time for a new FreeType release (Alexei Podtelezhnikov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 3 Apr 2018 11:47:33 +0100
> From: Nikolaus Waxweiler <madig...@gmail.com>
> To: Vincent Torri <vincent.to...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAM+=65LKmq3fVgpZn3a1JHEJhVQ8EL_BB7MwomTRLYmHfZwreA@mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Good :) Is it usable your your purposes? Is there a specific reason
> you compile in MSYS instead of using a native CMake build?
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 3 Apr 2018 11:52:53 +0100
> From: Nikolaus Waxweiler <madig...@gmail.com>
> To: Vincent Torri <vincent.to...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAM+=65LA9N4hdpkTFL9saAeK=JVB7YQYKLJtN3L=tyNHaxX=VQ@
> mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> (Oh, and: streamlining the build process for all build systems should
> make it much easier to add support for more. FreeType definitely needs
> more build systems.)
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 3 Apr 2018 12:13:27 +0100
> From: Nikolaus Waxweiler <madig...@gmail.com>
> To: Werner LEMBERG <w...@gnu.org>
> Cc: suzuki toshiya <mpsuz...@hiroshima-u.ac.jp>,        freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAM+=65+VDCyC5F1-DDSARMBeWVQnpPu9MVnTJRgGG44qMi
> u...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> > (1) A call to make should run on *all* platforms.  In other words, GNU
> make by itself had to produce an `ftconfig.h' file from the template.
>
> Run `diff -U2 ./include/freetype/config/ftconfig.h
> ./builds/unix/ftconfig.in` -- What's to be done about the #define
> differences?
>
> > Because this needs a bourne shell...
>
> That's horrible. `sed` should do the job I reckon.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 3 Apr 2018 13:22:09 +0200
> From: Vincent Torri <vincent.to...@gmail.com>
> To: Nikolaus Waxweiler <madig...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAMq1adoDL0fHFDM22AZxwD79r8G2c4E9vBs_9k9B0m=yGdA8zQ@mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Tue, Apr 3, 2018 at 12:47 PM, Nikolaus Waxweiler <madig...@gmail.com>
> wrote:
> > Good :) Is it usable your your purposes? Is there a specific reason
> > you compile in MSYS instead of using a native CMake build?
>
> MSYS2 is "native" in the sense that there is no additional DLL which
> is required (contrary to cygwin)
> andi said "native" because compiling with gcc is actually cross
> compilation (native would mean Visual Studio, and Visual Studio is so
> huge...)
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 3 Apr 2018 13:23:41 +0200
> From: Vincent Torri <vincent.to...@gmail.com>
> To: Nikolaus Waxweiler <madig...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAMq1adqadAOQyjnRsR9HnRwy1CYU=pPmcGkd3=ePx-byjygALg@mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Tue, Apr 3, 2018 at 12:52 PM, Nikolaus Waxweiler <madig...@gmail.com>
> wrote:
> > (Oh, and: streamlining the build process for all build systems should
> > make it much easier to add support for more. FreeType definitely needs
> > more build systems.)
>
> then you multiply the amount of work by the number of build systems
> each time you modify build systems.
>
> sticking to one build system with a good doc is the less error prone
>
> regards
>
> Vincent Torri
>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 3 Apr 2018 12:26:39 +0100
> From: Nikolaus Waxweiler <madig...@gmail.com>
> To: Vincent Torri <vincent.to...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAM+=65+aSTfb5adFxM-9M3+4YGRnpLQmCv_b_1AqDO9u+EUy8g@
> mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> > MSYS2 is "native" in the sense that there is no additional DLL which is
> required (contrary to cygwin)  andi said "native" because  compiling with
> gcc is actually cross compilation (native would mean Visual Studio, and
> Visual Studio is so huge...)
>
> Ah, okay. Maybe you find that my cleaned CMake build also suits your
> MSYS needs while being faster :)
>
> > sticking to one build system with a good doc is the less error prone
>
> Yes :D I'd throw the other stuff out in a heartbeat (I love purging
> legacy code) but I'm not the maintainer and Werner has a different
> opinion on this :)
>
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 3 Apr 2018 09:40:24 -0400
> From: Alexei Podtelezhnikov <apodt...@gmail.com>
> To: Nikolaus Waxweiler <madig...@gmail.com>
> Cc: Werner LEMBERG <w...@gnu.org>, freetype-devel
>         <freetype-devel@nongnu.org>
> Subject: Re: [ft-devel] Time for a new FreeType release
> Message-ID:
>         <CAJU=AjU2HpEu4z6s4XHwRngq6943AmE+NvTr8nBw05xZUN-k3Q@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> >
> > > Because this needs a bourne shell...
> >
> > That's horrible. `sed` should do the job I reckon.
> >
>
> To compile FreeType you need ANSI C compiler. [period]
> You can use whatever is in your toolbox, but you cannot require it.
> Any additional requirements are not acceptable. Therefore ftconfig.h is
> there to stay.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.nongnu.org/archive/html/freetype-devel/
> attachments/20180403/1a6e9adf/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Freetype-devel mailing list
> Freetype-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/freetype-devel
>
>
> ------------------------------
>
> End of Freetype-devel Digest, Vol 159, Issue 5
> **********************************************
>
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to