Installation and Deployment

@liteyear I have no remote configuration here at the moment. But IIRC, you can select it in the combo box just above the env variables. I would, however, try not to depend on LD_LIBRARY_PATH. I kitten dies, when you use it. I'd rather compile the application with a run path in CMake, pointing to the right libraries. I use LD_LIBRARY_PATH just for local experiments, when I want to load e.g. a development version of a public library.

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?

Ancient QtCreator installers can be found here: https://download.qt.io/archive/qtcreator/ Iirc QtCreator 5.x was the latest which was built with Qt5.

@Christian-Ehrlicher That was my guess too :)

Copying Axel's answer from https://forum.qt.io/topic/163746/cannot-access-https-code.qt.io-yocto-meta-qt6-connection-refused/6 code.qt.io is under a persistent DDOS attack. At this moment, the situation is under control and it should work normally. Access to large repositories remains limited.

@TN_robot Please post the actual error...

See this Wiki page. There's nothing more to install but yes, starting from the command line is easier.

The reason is that GitHub just zips the content of the repository. The official archives are ready to configure/build for the platform selected (.zip for Windows and tar.gz for unix like).

Sometimes you have bugs in one architecture and not the others. It might also just be a subtle difference in you settings, etc.

@Christian-Ehrlicher Ok, I got it. I will look into the source code and try to fix the warnings.