From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Sun, 22 Nov 2020 10:41:34 +0100 [thread overview]
Message-ID: <87blfplodt.fsf@Rainer.invalid> (raw)
In-Reply-To: <AM6PR02MB39911D760875108FF8703FAEE7FE0@AM6PR02MB3991.eurprd02.prod.outlook.com> (Hamish McIntyre-Bhatty via Cygwin-apps's message of "Sat, 21 Nov 2020 16:52:19 +0000")
Hamish McIntyre-Bhatty via Cygwin-apps writes:
> *bump* in case this went unnoticed.
It didn't, I just know that this GNOME crap will always need another 40
packages installed before I can even start looking.
> I know it's a pain checking these over because it takes so long to build
> them, but I would still very much appreciate it. I am already a
> maintainer for other packages, but AFAIK this doesn't give me the right
> to GTG myself.
Here's what I have so far:
1. Do not add the runtime packages to BUILD_REQUIRES (i.e if you have
zlib-devel, then don't add zlib). If there are runtime packages you
need for testing, list them on a separate line and comment that these
are needed for testing only (xclock, graphviz?). Currently we assume
the dependencies needed by cygport to be available always without
explicitly mentioining them (e.g. autoconf), although it doesn't hurt to
have them in.
2. The option --without-gnomeprint seems no longer available and would
be default anyway since gtkprint gets detected and used.
3. You should explicitly specify that you want to use the system regex
library, so add --with-regex=sys.
4. It should be possible to enable full STL now, so add --enable-stl.
5. If you copy the config.cache forward to the next run of configure you
can save a bit of time not rechecking stuff you already checked.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2020-11-22 9:41 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 [this message]
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=87blfplodt.fsf@Rainer.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).