From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Sat, 17 Oct 2020 09:04:26 -0600 [thread overview]
Message-ID: <ee14ec92-7010-a06c-e00d-ad0024de7efa@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB7PR02MB3996821F296F44A1E205754FE7000@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 2020-10-17 07:17, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 17/10/2020 01:21, Lemures Lemniscati via Cygwin-apps wrote:
>> On Fri, 16 Oct 2020 20:20:53 +0100, Hamish McIntyre-Bhatty via Cygwin-apps
>>> Just sending this out so I can update wxWidgets to 3.0.5.1. I've pulled
>>> in new patches from Fedora, but I can't find
>>> mirror://portage/x11-libs/wxGTK/files/wxGTK-3.0.3-collision.patch
>>> anywhere. Does anyone happen to have a copy of this?
>>>
>>> My hope is that it is no longer needed, but obviously I can't confirm
>>> that without actually having the patch. I haven't got any files uploaded
>>> yet because I'm doing a test build. If anyone has a copy of that
>>> patch/knows where to find it please let me know.
>> You can get them from one of the current src packages.
>> List of src files: https://www.cygwin.com/packages/x86_64/wxWidgets3.0-src/wxWidgets3.0-3.0.4-1-src
>> Package: http://mirrors.kernel.org/sourceware/cygwin/x86_64/release/wxWidgets3.0/
> Excellent, thanks :)
>
> I'll post again when I've got builds and have improved the cygport file
> (this one doesn't have build dependencies).
>
> It takes about 3-4 hours per build, somehow, so it might be a little
> while, but we'll see :)
Those mirrors should be part of cygport SRC_URI or PATCH_URI and will be
retrieved on download.
Portage is gentoo equivalent on which cygport is based and that patch hits some
make and bake file and translation sources as part of a patchset series:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e16e67f0678b264a04e96954a4593ddac3a9a32d
including also:
https://dev.gentoo.org/~leio/distfiles/wxGTK-3.0.3_p20180104.tar.xz
where you will have to figure out if you need to doenload and apply patches to
their sources or make a similar change to get the equivalent effect in your
cygport.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-10-17 15:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 19:20 Hamish McIntyre-Bhatty
2020-10-17 0:21 ` Lemures Lemniscati
2020-10-17 13:17 ` Hamish McIntyre-Bhatty
2020-10-17 15:04 ` Brian Inglis [this message]
2020-10-19 15:31 ` Hamish McIntyre-Bhatty
2020-10-21 13:57 ` Hamish McIntyre-Bhatty
2020-10-21 17:17 ` Brian Inglis
2020-10-21 18:39 ` Achim Gratz
2020-10-27 11:53 ` Hamish McIntyre-Bhatty
2020-10-27 13:16 ` ASSI
2020-10-28 2:21 ` Hamish McIntyre-Bhatty
2020-10-28 8:40 ` Achim Gratz
2020-10-30 19:39 ` Hamish McIntyre-Bhatty
2020-11-11 15:15 ` Hamish McIntyre-Bhatty
2020-11-11 17:36 ` Hamish McIntyre-Bhatty
2020-11-12 18:00 ` Hamish McIntyre-Bhatty
2020-11-21 16:52 ` Hamish McIntyre-Bhatty
2020-11-21 21:56 ` Brian Inglis
2020-11-22 9:43 ` Achim Gratz
2021-01-08 17:07 ` Hamish McIntyre-Bhatty
2021-01-08 17:15 ` Achim Gratz
2020-11-22 9:41 ` Achim Gratz
2020-11-23 12:53 ` Hamish McIntyre-Bhatty
2020-11-23 15:26 ` ASSI
2020-11-23 16:18 ` Hamish McIntyre-Bhatty
2020-11-23 19:16 ` ASSI
2020-11-23 19:24 ` Hamish McIntyre-Bhatty
2020-11-23 19:34 ` Hamish McIntyre-Bhatty
2020-11-23 20:05 ` ASSI
2020-11-23 20:11 ` Hamish McIntyre-Bhatty
2020-11-24 10:15 ` Hamish McIntyre-Bhatty
2020-11-24 10:43 ` Hamish McIntyre-Bhatty
2020-11-24 19:51 ` Hamish McIntyre-Bhatty
2020-11-25 10:02 ` Hamish McIntyre-Bhatty
2020-12-09 20:55 ` Hamish McIntyre-Bhatty
2020-12-13 20:12 ` Marco Atzeri
2020-12-14 9:46 ` Hamish McIntyre-Bhatty
2020-12-14 20:21 ` Marco Atzeri
2020-12-15 1:49 ` Hamish McIntyre-Bhatty
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=ee14ec92-7010-a06c-e00d-ad0024de7efa@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@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).