From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [ATTN MAINTAINER] qt5-base
Date: Fri, 01 Jan 2021 17:01:54 +0100 [thread overview]
Message-ID: <87sg7kmyrx.fsf@Rainer.invalid> (raw)
So I thought that it woöuld be good to update Qt5 before it becomes Qt6…
unfortunately the version in Cygwin is 5.9.4 while 5.15.2 is current, so
there is quite a bit of changes to wade through. It doesn't help that
that the Cygwin patches never got upstreamed or accepted (the net result
is the same). I think I've got the whole thing cleaned up so that it
should work, but there is one change that stumps me:
In 5.9.4 the QT5 libraries were linked via
-L/mnt/share/packages/qt5-base-5.9.4-2.src/qt5-base.x86_64/build/lib -lQt5Core
while in 5.15.2 that has changed to
/mnt/share/packages/qt5-base/qt5-base.x86_64/build/lib/cygQt5Core.dll
This nixes the fixup that was supposed to get the correct name there
(which I had to disable anyway because it now mucks up the target name
for the .prl stuff). I have no good idea where to fix that up, I think
I'd want the link library (.dll.a) there if I need to keep the absolute
path. For now I've done a monkey patch around that with a hardlink, but
there must be a better way of doing it… The compile now goes through, I
later get an error because it tries to use some tools that I haven't yet
installed.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next reply other threads:[~2021-01-01 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 16:01 Achim Gratz [this message]
2021-01-01 16:49 ` Achim Gratz
2021-01-01 22:19 ` Mark Geisert
2021-02-19 5:25 ` Marco Atzeri
2021-02-19 11:49 ` Marco Atzeri
2021-02-19 20:34 ` Achim Gratz
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=87sg7kmyrx.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).