From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Updated cygport for for wxwidgets 3.0 package
Date: Sat, 07 Sep 2019 19:12:00 -0000 [thread overview]
Message-ID: <87lfuzapks.fsf@Rainer.invalid> (raw)
In-Reply-To: <AM6PR04MB6101602A509DF2F8E7652FEEE7B50@AM6PR04MB6101.eurprd04.prod.outlook.com> (Hamish MB's message of "Sat, 7 Sep 2019 18:48:21 +0000")
Hamish MB writes:
> 3: I needed these in order to build without the patches. I'm not sure
> why, but these aren't needed when the patches are used. This is
> documented at https://forums.wxwidgets.org/viewtopic.php?f=19&t=46091
It's quite obvious that nobody in that thread has any first-hand
experience with Cygwin and yet they give (mostly bogus as a result of
that) advice.
As with many other projects, upstream often doesn't know about Cygwin at
all, makes assumptions that are outdated by decades or just plain
guesses wrong. If the project happens to have a native Windows port,
these wrong assumptions are often more widespread, unfortunately. They
can be in the configury, the Makefiles or the sources themselves, so
getting things right can take a while. If you need to update a package
you're off to a way better start if you take the existing cygport for
the previous version and then figure out what changes need to apply in
top of that; rather than starting from scratch. If you are unsure what
a patch does, ask the current maintainer (on this list) rather than just
yanking it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2019-09-07 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 16:37 Hamish MB
2019-09-05 19:35 ` Yaakov Selkowitz
2019-09-05 19:42 ` Hamish MB
2019-09-05 21:19 ` Yaakov Selkowitz
2019-09-06 8:58 ` Hamish MB
2019-09-07 15:08 ` Jon Turney
2019-09-07 18:48 ` Hamish MB
2019-09-07 19:12 ` Achim Gratz [this message]
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=87lfuzapks.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).