public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: cygwin@cygwin.com
Subject: mingw64-x86_64-icu / mingw64-i686-icu 64.2
Date: Fri, 26 Apr 2019 19:33:00 -0000	[thread overview]
Message-ID: <7ed56e5b-f4cc-92e6-d85b-5e8e5ef77864@weilnetz.de> (raw)
In-Reply-To: <5656d1a4-0b58-177b-0347-15682b41d87d@weilnetz.de>

The following experimental updates are not available from Cygwin, but
from my personal website https://qemu.weilnetz.de/test/cygwin/local/:

mingw64-x86_64-icu 64.2
mingw64-i686-icu 64.2

I tested the binary packages using a short test program
(https://github.com/tesseract-ocr/tesseract/issues/1625#issuecomment-395166694).
Maybe someone else has other tests and wants to try the new packages.

Both packages are currently unmaintained in Cygwin (old version 57.1,
broken mingw64-x86_64-icu). See issue
https://github.com/cygwinports/mingw64-x86_64-icu/issues/1 and pull
request https://github.com/cygwinports/mingw64-x86_64-icu/pull/2. See
also https://sourceware.org/ml/cygwin/2018-10/msg00209.html and
https://cygwin.com/ml/cygwin/2018-06/msg00222.html.

I need those packages to build Tesseract for Windows.

I would also like to contribute packages for Leptonica (also needed for
Tesseract): mingw64-x86_64-leptonica and mingw64-i686-leptonica.
Building such packages is easy, but how can I can get them into the
official package distribution?

Regards
Stefan Weil


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2019-04-26 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 14:54 [ANNOUNCEMENT] icu 63.1-1 Ken Brown
2018-10-22 15:01 ` Stefan Weil
2018-10-24 15:33   ` Ken Brown
2019-04-26 19:33   ` Stefan Weil [this message]
2019-04-27  8:54     ` mingw64-x86_64-icu / mingw64-i686-icu 64.2 Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ed56e5b-f4cc-92e6-d85b-5e8e5ef77864@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).