public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter Quiring <pquiring@gmail.com>
To: cygwin@cygwin.com
Subject: Re: mingw include path missing Qt
Date: Mon, 23 Oct 2017 12:19:00 -0000	[thread overview]
Message-ID: <CA+3dX1zqAbvU_piqKGnvwLpt3x0gfcXNVXTN=inVdSyUmCFaEg@mail.gmail.com> (raw)
In-Reply-To: <cd278157-ea3e-6f29-25e9-a963fe8745a7@gmail.com>

I didn't see it was in /usr/include/qt5 as well.  That would be a
standard location.  Thanks.

On Fri, Oct 20, 2017 at 2:13 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> On 20/10/2017 20:00, Peter Quiring wrote:
>>
>> Another issue I'm having with mingw is the Qt headers are not in the
>> include path.
>>
>> So I always have to add
>> -Ic:\cygwin\usr\x86_64-w64-mingw32\sys-root\mingw\include\qt5 to get
>> the Qt headers included.
>>
>> Is there a correct way to do this?
>>
>> Thanks.
>
>
> this is true for any Qt5 header, not just for mingw.
>
> $ ls -1 /usr/include/qt5
> Qsci
> QtCLucene
> QtConcurrent
> QtCore
> QtDBus
> ....
>
> The build system should add the proper include path
> if need qt5, or you need to do it.
>
> Regards
> Marco
>
>
>
>
>
>
>
> --
> 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
>



-- 
Peter Quiring

--
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

      reply	other threads:[~2017-10-23 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 18:00 Peter Quiring
2017-10-20 18:13 ` Marco Atzeri
2017-10-23 12:19   ` Peter Quiring [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='CA+3dX1zqAbvU_piqKGnvwLpt3x0gfcXNVXTN=inVdSyUmCFaEg@mail.gmail.com' \
    --to=pquiring@gmail.com \
    --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).