[Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

[Jérôme Godbout]

Maybe a fallback check could be done first, Cygwin add env variables: OSTYPE which can be check to see if this is Cygwin. Or maybe uname detection to confirm. Could be more robust then path executable. With Windows Linux subsystem taking traction versus Cygwin, this check can become even more unreliable.


From: Interest <interest-bounces at qt-project.org> On Behalf Of Kai Köhne
Sent: December 16, 2020 4:07 AM
To: Alexander Dyagilev <alervdvcw at gmail.com>; interest <Interest at qt-project.org>
Subject: Re: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows

Hi,

Do you have a sh.exe in PATH? If so , qmake assumes you’re running in a Cygwin shell.

Regards

Kai

From: Interest <interest-bounces at qt-project.org<mailto:interest-bounces at qt-project.org>> On Behalf Of Alexander Dyagilev
Sent: Wednesday, December 16, 2020 9:20 AM
To: interest <Interest at qt-project.org<mailto:Interest at qt-project.org>>
Subject: [Interest] shell_path, QMAKE_COPY, etc. are broken when building for Android under Windows


Hello,

Is it known bug? Is there workaround?

What I mean:

The following in .pro file:

message(QMAKE_COPY = $$QMAKE_COPY)
message(shell path for PWD is: $$shell_path($$PWD))

Generates the following outputs (under Windows OS):

When building for Windows (there is no bug):
Project MESSAGE: QMAKE_COPY = copy /y
Project MESSAGE: shell path for PWD is: C:\Work\Source\fdm-qml\ui

When building for Android (there is bug, things gets unusable):
Project MESSAGE: QMAKE_COPY = cp -f
Project MESSAGE: shell path for PWD is: /C/Work/Source/fdm-qml/ui

Windows does not understand cp command and the path obviously wrong too.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20201216/f8e9000d/attachment.html>