> On Wednesday, 21 April 2021 10:39:01 PDT Giuseppe D'Angelo via Interest wrote:
> > But no $X. I'm still not sure what $PROJ means.
>
> The way the example was given, the string "$PROJ" will be written literally to
> the Makefile. Make will then interpret it as $(P)ROJ, which is likely not what
>
On Wednesday, 21 April 2021 10:39:01 PDT Giuseppe D'Angelo via Interest wrote:
> But no $X. I'm still not sure what $PROJ means.
The way the example was given, the string "$PROJ" will be written literally to
the Makefile. Make will then interpret it as $(P)ROJ, which is likely not what
you want.
Den ons 21 apr. 2021 kl 20:43 skrev Elvis Stansvik :
>
> Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
> >
> >
> >
> > > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > > From: "Thiago Macieira"
> > > To: interest@qt-project.org
&
guy on windows qmake
> Sent: Wednesday, April 21, 2021 at 1:14 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Help a unix guy on windows qmake
>
> On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> > Now, when compil
Den ons 21 apr. 2021 kl 20:43 skrev Elvis Stansvik :
>
> Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
> >
> >
> >
> > > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > > From: "Thiago Macieira"
> > > To: interest@qt-project.org
&
Den ons 21 apr. 2021 kl 19:49 skrev Jason H :
>
>
>
> > Sent: Wednesday, April 21, 2021 at 1:14 PM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Help a unix guy on windows qmake
> >
> > On Wednesd
> Sent: Wednesday, April 21, 2021 at 1:14 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Help a unix guy on windows qmake
>
> On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> > Now, when compiling, regardless of
On 21/04/2021 19:14, Thiago Macieira wrote:
qmake does not expand environment variables at all.
$ X=A qmake Y=b /dev/stdin -o /dev/null <<<'message(r = $X $$Y)'
Project MESSAGE: r = $X b
AFAIK, there's distinct syntax for everything:
$$X is a qmake variable called X
$$(X) is an environment va
On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> Now, when compiling, regardless of shadow build or not, refer to the libs by
> adding to the project: +++ project.pro
> + mingw {
> + INCLUDEPATH += $PROJ/libraries/win/include
> + LIBS += -L$PROJ/libraries/win/$ARCH -lvendor
> + }
>
On Wednesday, 21 April 2021 09:54:09 PDT Jason H wrote:
> MinGW is not x64? It's running on a fairly recent windows 10 machine.
"mingw32" means "Minimal GNU for Win32" and Win32 is the name of the API set.
It's historical and applies to 64-bit too. That's why the mkspecs for windows
are win32-ms
On Wednesday, 21 April 2021 08:49:02 PDT Jason H wrote:
> I'm having a bugger of a time getting a project working under windows. I've
> been doit under mac and linux for the last many years. What is the proper
> scope? Allegedly these are listed in C:\Qt\$ver\$compiler\mkspecs, however
> there are
> Sent: Wednesday, April 21, 2021 at 12:04 PM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Help a unix guy on windows qmake
>
> On 21/04/2021 17:49, Jason H wrote:
> > What is the proper scope? Allege
On 21/04/2021 17:49, Jason H wrote:
What is the proper scope? Allegedly these are listed in
C:\Qt\$ver\$compiler\mkspecs, however there are no win64 ones. I'm using mingw.
mingw is the proper scope. When in doubt, look at Qt's own sources.
src/angle/src/libEGL/libEGL.pro
19:mingw:equals(
I'm having a bugger of a time getting a project working under windows. I've
been doit under mac and linux for the last many years.
What is the proper scope? Allegedly these are listed in
C:\Qt\$ver\$compiler\mkspecs, however there are no win64 ones. I'm using mingw.
Why is there no $PROJ variabl
14 matches
Mail list logo
