[Interest] Help a unix guy on windows qmake

[Giuseppe D'Angelo]

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(QT_ARCH, i386): DEF_FILE = $$ANGLE_DIR/src/libEGL/$${DEF_FILE_TARGET}_mingw32.def
> 
> src/angle/src/libGLESv2/libGLESv2.pro
> 9:    mingw: equals(QT_ARCH, i386): DEF_FILE = $$ANGLE_DIR/src/libGLESv2/$${DEF_FILE_TARGET}_mingw32.def


> Why is there no $PROJ variable for linking when shadow building?
> $PWD resolves to the shadow build dir, it seems?
> How do I properly refer LIBS to $PROJ/libraries/x64/mylib.lib?
> How do I properly refer INCLUDEPATH to $PROJ/libraries/mylib.h?
> You know what $PROJ means, but for some reason this concept doesn't exist in qmake yet?

I... don't quite know what $PROJ means *for you*? :)

Do you mean $$OUT_PWD? Do you mean $$shadowed($$PWD)?


Thanks,
-- 
Giuseppe D'Angelo | giuseppe.dangelo at kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4329 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20210421/ff32c85f/attachment-0001.bin>