Installation and Deployment

I cannot reproduct that, the installer addOperation simpy calls QDir::root().mkpath(dirName) https://doc.qt.io/qt-6.9/qdir.html#mkpath Could you double check that the file with that name did not already exist? Then QDir::mkpath probably is not able to make the folder with the same name

@0b_sure I've lost two days googling, solving this problem ... your solution did the trick! TY!

@masa123 said in Qt Creator 18.0.1 lags for 1-3 sec: I havent done anything after the installation other than setting up the android virtual device. This looks like QTCREATORBUG-27311: QtCreator 7: lag every 10 seconds. Qt Creator has an issue with Android on Windows when is doing some adb startup on the UI thread. Please do update the bug report with the specific details that your development machine has.

@ewalve said in Qt doesn't build statically in CMake: I can't see anywhere. https://wiki.qt.io/Building_a_static_Qt_for_Windows_using_MinGW

@MHermann If you want to know why a module was enabled or disabled in configure run then check the content of config.log file.

Worth a shot. Did you run macdeployqt in verbose mode to check if there was any error message regarding the missing libraries ?

Alas the only other thing in that combo box is "Clean Environment" and it doesn't make any difference. Not even to the list of variables printed by env. Yes, I'm deep in kitten killing territory. I'm targeting a remote device because I'm cross-compiling - it's literally my development device. So being able to fiddle with environment variables and kill a few kittens is a normal part of the process. Same as you might use QT_QPA_PLATFORM=eglfs build/myApp or other flags temporarily when developing locally. In other words, if I can't set environment variables on the target (like I can for local run environments), then the "run on remote device" feature is not useful. Better (and way quicker, incidentally) to scp the built binary to the target and run it there manually. But that would be a pity - surely the "Environment" configuration is supposed to allow this?

I don't have Windows 11 so I can't be sure ... however, it looks like the Roaming subfolder is not a good idea, according to this page: https://learn.microsoft.com/en-us/windows/apps/design/app-settings/store-and-retrieve-app-data#roaming-data

I did not. I assume then than no one is really using it for real projects. My next move when this becomes a higher priority again is going to be to start using AI to help with this since those models probably have good knowledge of the nuitka docs.

sorry, it says “this application can‘t run on your mashine，if you want to find the fit version ,please connect with provider” I also try 4.9.0 installer，it can work。but 4.10.0 can not。

Ok. Thank you. Anyway, code.qt.io is accessible again. I can even do git clone --branch v6.10.1 git://code.qt.io/qt/qt5.git . which means all of the submodules are also cloned from code.qt.io. The configuring process has been successful. Anyway. if code.qt.io is not accessible again, can I substitute all the code.qt.io part of each git submodule set-url -- path/path/path https://code.qt.io/path/repository.git to codereview.qt-project.org? I'm talking about Qt6

Well I did the most basic thing I could think of: arm-dey-linux-gnueabi-strip --strip-unneeded lib/*.so.6.8.3 lib/*.a And whaddya know: [image: ecda362c-1396-4f63-80a1-ae9c81c99f20.png] Why was that step necessary? I can't find mention of it anywhere, even in the Building Optimized Qt page.

Also not a lawyer here. Your obligation is to comply with LGPL. That means your app has to be linked dynamically to Qt (not static) you have to include a license note saying explicitly that you are using Qt under LGPL users must be able to replace the Qt version with another, without any restrictions (no hardware / software tricks to put a stick in the wheel).

@cjhinza Hello! I have the same error while building Qt 6.10.1 from source on Ubuntu 22.04. Here is a part of my Dockerfile: ... RUN git clone https://github.com/openssl/openssl.git /openssl ENV ANDROID_NDK_ROOT=/AndroidSdk/ndk/29.0.14206865 ENV API_LEVEL=28 ENV HOST_OS=linux-x86_64 ENV PATH=$ANDROID_NDK_ROOT/toolchains/llvm/prebuilt/$HOST_OS/bin:$PATH WORKDIR /openssl RUN ./Configure shared android-x86 -D__ANDROID_API__=28 RUN make -j$(nproc) SHLIB_VERSION_NUMBER= build_libs ENV OPENSSL_DIR=/usr/local/OpenSSL-Android/x86 RUN make install DESTDIR=$OPENSSL_DIR RUN mkdir -p /qt6-build-android-x86 WORKDIR /qt6-build-android-x86 RUN ../qt6/configure -prefix /usr/local/Qt-Android-x86 -opensource -confirm-license -release -force-debug-info -separate-debug-info -c++std c++17 \ -pch \ -platform linux-clang \ -vulkan -opengl es2 \ -make tools -nomake examples -nomake tests \ -skip qtlocation \ -android-sdk /AndroidSdk -android-ndk /AndroidSdk/ndk/29.0.14206865 -android-ndk-platform android-28 -android-abis x86 \ -qt-host-path /usr/local/Qt-Linux \ -openssl \ -DOPENSSL_ROOT_DIR=/usr/local/OpenSSL-Android/x86 \ -DOPENSSL_LIBRARIES=/usr/local/OpenSSL-Android/x86/lib \ -DOPENSSL_INCLUDE_DIR=/usr/local/OpenSSL-Android/x86/include I used the same link as you to build OpenSSL. Added/removed this block: RUN cp libcrypto.so $OPENSSL_DIR/lib/libcrypto_3.so RUN cp libssl.so $OPENSSL_DIR/lib/libssl_3.so RUN cp -r include/openssl $OPENSSL_DIR/include/ WORKDIR $OPENSSL_DIR/lib RUN patchelf --set-soname libcrypto_3.so libcrypto_3.so RUN patchelf --set-soname libssl_3.so libssl_3.so RUN patchelf --replace-needed libcrypto.so libcrypto_3.so libssl_3.so Tried different paths: -DOPENSSL_ROOT_DIR=/usr/local/OpenSSL-Android/x86/usr/local -DOPENSSL_LIBRARIES=/usr/local/OpenSSL-Android/x86/usr/local/lib -DOPENSSL_INCLUDE_DIR=/usr/local/OpenSSL-Android/x86/usr/local/include but didn't solve the problem: ... CMake Error at qtbase/cmake/QtBuildInformation.cmake:554 (message): Feature "openssl_runtime": Forcing to "ON" breaks its condition: TEST_opensslv11_headers OR TEST_opensslv30_headers Condition values dump: TEST_opensslv11_headers = "FALSE" TEST_opensslv30_headers = "FALSE" ... CMake Error at qtbase/cmake/QtTargetHelpers.cmake:1594 (message): WrapOpenSSLHeaders::WrapOpenSSLHeaders is not a valid target. Call Stack (most recent call first): qtbase/src/plugins/tls/openssl/CMakeLists.txt:61 (qt_internal_add_target_include_dirs) ... if you or someone knows how to fix this annoying issue, I would be very appreciative!

Ah, that was also the solution for command line install! To be clear: ./qt-online-installer-linux-x64-online.run --root <rootpath> install <package> only works for the first install. After that you have to use the installed Maintenance Tool, in the same way: <rootpath>/MaintenanceTool install <package2>

Try adding these to your CMakeLists.txt: find_package(PkgConfig) pkg_check_modules(GST REQUIRED gstreamer-1.0>=1.4 gstreamer-app-1.0>=1.4) target_link_libraries( ${MODULE_NAME} PUBLIC . . . ${GST_LIBRARIES} ) target_include_directories( ${MODULE_NAME} PUBLIC . . . ${GST_INCLUDE_DIRS} ) I hope this helps.

I just ran into this issue on a Mac running Tahoe. The above solution (deleting the %General section) worked for me. One thing I know that happened recently is that the Command Line Tools for XCode were updated since I last ran Qt Creator. Maybe this is related?