From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Mon, 23 Nov 2020 16:26:37 +0100 [thread overview]
Message-ID: <87v9dwt7pu.fsf@Otto.invalid> (raw)
In-Reply-To: <AM6PR02MB399173DEE504ECD5C7D94BC6E7FC0@AM6PR02MB3991.eurprd02.prod.outlook.com> (Hamish McIntyre-Bhatty via Cygwin-apps's message of "Mon, 23 Nov 2020 12:53:22 +0000")
Hamish McIntyre-Bhatty via Cygwin-apps writes:
> 1. I have separated these onto another line. I've kept this enabled for
> manual testing, and also because other things in my Cygwin install need
> some of these dependencies - I can't easily remove to be 1000% sure that
> none of them are needed during building. It seems wxWidgets hasn't
> documented optional build dependencies very clearly.
Graphviz is actually needed for building the docs I've found.
> 4. Okay, trying that in this build. Not sure how to test that any
> features need that are working, so I'll have to research that.
Specifically, copying the config.cache from base to both of the gtk{2,3}
builds should work, but not gtk2->3. I've re-arranged the cygport file
to first configure all three (makes it easier to hunt for differences),
then build in reverse order.
> I'll wait on the CI system then, this takes hours to build even on my
> Ryzen 3600, especially on 32-bit Cygwin.
That's odd. I've built on a 4-core/8-thread Haswell in well under two
hours per architecture and I haven't seen memory peak above 8GiB. You
said you are building in a VM, perhaps you should reduce the number of
threads there a bit. If the VM starts contending for host resources
things _will_ get ugly.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2020-11-23 15:26 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 [this message]
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=87v9dwt7pu.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).