Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P2: Important
-
Resolution: Done
-
Affects Version/s: 5.11
-
Fix Version/s: 5.12.0 Alpha
-
Component/s: Build tools: qmake
-
Labels:None
-
Platform/s:
Android
-
Commits:64d63d036c8938b88fa47e8036f1ebe0279b75cf
Description
... at least on Windows with builds using -prefix...
The install_target target which is generated looks like this:
install_target: first FORCE @if not exist C:$(INSTALL_ROOT:@msyshack@%=%)\QtBuild\clean-dev\android-x86\tests\libtst_qmath.so mkdir C:$(INSTALL_ROOT:@msyshack@%=%)\QtBuild\clean-dev\android-x86\tests\libtst_qmath.so & if not exist C:$(INSTALL_ROOT:@msyshack@%=%)\QtBuild\clean-dev\android-x86\tests\libtst_qmath.so exit 1 -$(QINSTALL_PROGRAM) $(QMAKE_TARGET) C:$(INSTALL_ROOT:@msyshack@%=%)\QtBuild\clean-dev\android-x86\tests\libtst_qmath.so\$(QMAKE_TARGET)
You are then supposed to run
mingw32-make install INSTALL_ROOT=path\to\android-build
Which then, unsurprisingly, fails.
For comparison; this is how it would normally be generated:
install_target: first FORCE @if not exist $(INSTALL_ROOT:@msyshack@%=%)\libs\x86 mkdir $(INSTALL_ROOT:@msyshack@%=%)\libs\x86 & if not exist $(INSTALL_ROOT:@msyshack@%=%)\libs\x86 exit 1 -$(QINSTALL_PROGRAM) $(QMAKE_TARGET) $(INSTALL_ROOT:@msyshack@%=%)\libs\x86\$(QMAKE_TARGET)
Edit: I can also repro this issue for tests outside of Qt.