From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Can't compile port qtermwidget
Date: Mon, 10 Feb 2020 14:55:00 -0000 [thread overview]
Message-ID: <b3aa3c19-9cdd-3437-84a4-5a399e050250@cs.umass.edu> (raw)
In-Reply-To: <fb3fb6c1-8073-5ad6-c07a-00d662725e16@galbraiths.ca>
On 2/9/2020 10:21 PM, Paul Galbraith via cygwin wrote:
> On 2020-02-09 5:18 p.m., Eliot Moss wrote:
>> I am not Qt savvy, but I can think of two generic things to check:
>>
>> - The Qt version in the cygwin libraries you have, versus what qtermwidget expects.
>>
>> - The version of the C compiler (gcc keeps evolving, and that sometimes breaks things).
>> Â Maybe there is info on the web about Qt issues with various version of gcc.
>
> Thanks Eliot. The package works with the current Qt libs so I'm working under the assumption that
> the Qt version is Ok.
>
> I've figured out that if -DQT_NO_CAST_FROM_ASCII and -DQT_NO_CAST_TO_ASCII are removed from the
> compile directives, the situation improves drastically (at least on the first file I tried to
> compile manually, the number of compile errors goes from dozens to zero). But, I don't know why
> Cmake is adding those directives.
I wonder ... are there relevant ./configure options? EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-02-10 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 22:11 Paul Galbraith via cygwin
2020-02-09 22:18 ` Eliot Moss
2020-02-10 3:21 ` Paul Galbraith via cygwin
2020-02-10 14:55 ` Eliot Moss [this message]
2020-02-15 0:29 ` Paul Galbraith via cygwin
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=b3aa3c19-9cdd-3437-84a4-5a399e050250@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@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).