Installation and Deployment

I would venture that the version of chromium that was provided with 6.2.9 does not support arm builds. You should consider updating Qt to a more recent version. 6.2.9 is very outdated.

Upgrading to Qt installer framework 4.10 (from 4.9) has solved my problem. For future reference, I have a tag like this in my config.xml: <ControlScript>install.qs</ControlScript>. In the config directory, there must be a install.qs file with the script.

I managed to compile the drivers using thecodemonkey guidlines as hinted by @nyquistjack and other web resources. But a lot is required to make the drivers work for WebAssembley.

Downgraded Qt VS Tools Extension to 3.2.0 and that got it working.

@ValeryK said in Qt Installer Framework: online installation of Matlab Runtime 2020b as a component: What are the QIF capabilities for implementing such behavior? For something as complex as this could you installer.performOperation("Execute", ...), like in https://stackoverflow.com/questions/43901488/how-to-run-an-executable-file-in-qt-installer-framework, a program or script you supply which goes through the various steps? (There are also individual Delete and Extract operations there if wanted.)

It's all documented here and it works out of the box. I personally don't use -skip. I explicitly select the submodules I want to build. I always build w/o prefix into directories outside the source tree. E.g. like that: ../dev/configure -developer-build -xcb -nomake examples -make tests -submodules qtdeclarative ninja

And why do you don't use english in the bug report? Please fix.

To answer my own question! I used "Add New Project Property Sheet" to add a property sheet called vcpkg. I told it to save it a file called vcpkg.props in the root directory of the solution. I then configured the two User Macros as above. I then used "Add Existing Property Sheet" to add this file to all configurations of all the projects in the solution. Sounds rather awkward, but it does seem to work.

Solution found, I edited the vcpkg.props file with gets loaded after Qt so that it sets the environment variable: <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <ImportGroup Label="PropertySheets" /> <PropertyGroup Label="UserMacros"> <VCPKG_KEEP_ENV_VARS>QTDIR</VCPKG_KEEP_ENV_VARS> <QTDIR>$(QtInstallDir)</QTDIR> </PropertyGroup> <PropertyGroup /> <ItemDefinitionGroup /> <ItemGroup> <BuildMacro Include="VCPKG_KEEP_ENV_VARS"> <Value>$(VCPKG_KEEP_ENV_VARS)</Value> <EnvironmentVariable>true</EnvironmentVariable> </BuildMacro> <BuildMacro Include="QTDIR"> <Value>$(QTDIR)</Value> <EnvironmentVariable>true</EnvironmentVariable> </BuildMacro> </ItemGroup> </Project>

@Pudying Please read what @JKSH wrote

@xalioth Thanks that is the answer I have been looking for. My current script is now as follows and seems to have worked, the build has just finished so I will now see what QtCreator makes of it. #! /bin/sh rm -r build-qt mkdir build-qt cd build-qt ../configure -prefix /opt/qt-android/ -qt-host-path /opt/qt6/ -android-abis arm64-v8a -android-sdk /opt/android/sdk/ -android-ndk /opt/android/sdk/ndk/27.2.12479018 -skip qtwebengine -openssl-linked -- -D OPENSSL_ROOT_DIR="/work/Qt-Android/android_openssl/ssl_3/arm64-v8a" exit $?

Xeyes shows that the application is using X11. Once I'll find time, I try to force it to use Wayland.

I have just experienced what looks like the exact same error. Even the same line number. Clang++-19, Qt5-base 5.15.17, Linux Alpine 3.22 ../../include/QtNetwork/5.15.17/QtNetwork/private/../../../../../../src/network/socket/qnet_unix_p.h:120:29: error: cannot initialize a parameter of type 'socklen_t *' (aka 'unsigned int *') with an rvalue of type 'int *' 120 | fd = ::accept4(s, addr, static_cast<QT_SOCKLEN_T *>(addrlen), sockflags); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I believe it is a result of the defines in qtplatformdefs.h, where linux clang & linux llvm are implemented with opposite logic to linux g++? (Alpine will be the default #else in both cases, because it is MUSL, not GLIBC. One will be socklen_t and the other will be the offending int. Swapping the logic to match g++ is probably a hack, but it then compiles ok on Alpine.)

Speaking from my own past experience with the person/team managing aqt, you can expect a helpful reply by interacting with that project here: https://github.com/miurahr/aqtinstall/issues

ok so judging by everyone's responses i realised it wasn't that the code was out of date and that creator 17 needed updated instructions, rather there was something wrong with my setup. so in case anyone else has this problem with gnome desktop environment, the culprit is gnome's default terminal app "Console". this app has a binary called kxg and i couldn't figure out what instruction to give to creator to launch it. so i installed gnome-terminal and made this the default terminal app. under environment variables in the manage kits section, the terminal command is gnome-terminal -x. this seems to have solved the problem. thanks to everyone who replied. it set me in the right direction!

@Puneeth_BR Deploy your app properly first. See https://doc.qt.io/qt-6/deployment.html

AFAIK, no, you don't need a company account unless you are working for a company for that application.