From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Sun, 13 Dec 2020 21:12:13 +0100 [thread overview]
Message-ID: <57172955-f23a-0046-e0ef-5c932b052586@gmail.com> (raw)
In-Reply-To: <DB7PR02MB39967A3DB2DCF72C83A5605FE7CC0@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 09.12.2020 21:55, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 25/11/2020 10:02, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> Okay, so attached is my latest cygport file. I'm still building for
>>> 32-bit, so I'll upload and link to the new packages tomorrow.
>>>
>>> Changes:
>>>
>>> - Split BUILD_REQUIRES across two lines for definitely build time and
>>> probably only runtime deps.
>>>
>>> - Use system regex library explicitly.
>>>
>>> - Removed obsolete --without-gnomeprint option.
>>>
>>> - Use gnomevfs (old bug no longer seems to apply).
>>>
>>> I tried using the STL, but it results in libraries that don't work as:
>>>
>>> #1: the wxwidgets demos either segfault instantly or just exit instantly.
>>>
>>> #2: wxpython no longer works and returns the No such process error above.
>>>
>>> Hamish
>> Okay, cygport file attached again and the new packages can be had from
>> https://www.hamishmb.com/files/cygwin-temp/ as before.
>>
>> Hamish
>
> *bump*
>
> Would be good to get this verified so I can get on to other things for
> Cygwin.
>
> Hamish
>
it builds and packages fine.
but I tried to build the tests on gtk3/tests
make test.exe
and it fails
Regards
Marco
next prev parent reply other threads:[~2020-12-13 20:12 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
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 [this message]
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=57172955-f23a-0046-e0ef-5c932b052586@gmail.com \
--to=marco.atzeri@gmail.com \
--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).