Installation and Deployment

Okay, I have now built a minimal QtWebengineCore and QtCore app. This also does not run, and I receive no feedback when I call it from the console. However, the environment is suitable for a large QtGui app.

I have copied the sysroots directory into my system where Qt compilation environment is set up. Below is the only file available in the sysroots directory. tisdk/build/arago-tmp-default-glibc/sysroots/am335x-evm/imgdata/tisdk-default-image.env Note: I am using a am335x-evm custom board. Please suggest how to include the sysroots directory into the compilation process through command line arguments. Also, let me know what the contents of the sysroots directory should look like.

This solves any display related issues from within docker containers docker run -it --name $CONTAINER_NAME --network host -e DISPLAY -e TERM -e QT_X11_NO_MITSHM=1 $IMAGE_NAME bash

@Christian-Ehrlicher: With Ubuntu's cross compiler "arm-linux-gnueabi-..." a build was possible, not yet tested on target. Thanks!

Came across the same issue today with Qt 6.7.2 on macOS Ventura when building my app with GCC 14.2.0 (in C++23 mode). That is, because Qt was built with Apple Clang (14.0.0) which does not set _GLIBCXX_USE_CXX11_ABI=1. Inline methods (like QString::toStdString, QVector::toStdVector, etc...) are fine because they are compiled with the same C++ ABI as used in the application. That does no longer seems to be the case, because QByteArray::toStdString() is not defined in its header. Just for reference, I get the following linker errors: Undefined symbols for architecture x86_64: "QByteArray::toStdString[abi:cxx11]() const", referenced from: QString::toStdString[abi:cxx11]() const in main.cpp.o ld: symbol(s) not found for architecture x86_64

Hi, In addition to what @Axel-Spoerl wrote: are you using the Windows Subsystem for Linux ? Since you mention KStars, they have a Windows build so why not use that one directly ?

@mdebellis said in Finding a Kit for Basic Tutorial: I want to use QT with Python. In that case you should use PyQt (https://wiki.python.org/moin/PyQt) or PySide (https://wiki.qt.io/Qt_for_Python). The online installer you used is for C++ development.

@davidwedel So it looks like maybe someone was playing with Qt and switched default debugging off and that's how it got released with this file in it, even if no Qt! :) Naughty Fedora people!

What did you set to change the output directory of your libs? I'm having the same issue, can't change the output directory of the qt_generate_deploy_app_script. When I tried by setting CMAKE_INSTALL_LIBDIR, I get RPATH errors and can't make the package successfully.

is it there any incompatibility between Jetson Nano Hardware/Sofware and qtWebView? (aarch64+Ubuntu 18.04) Thanks for your answers.

@Scarab said in Static Qt Error: Qt version is not properly installed, please run make install: "pass the relocatable flag to configure". I don't know how to do that either, there is no configure field in the Qt versions tab "configure" is the command you execute before you build Qt. You need to pass relocatable flag to configure before you actually build Qt.

I think you just have to keep trying different mirrors. Are you claiming every one of them returns Forbidden? That would be different.

Hi and welcome to devnet, You should take a look at the content of the tests run by the configure script to see what exactly failed with regard to EGLFS. The NVIDIA forum might also contain some hints.

Then explicitly call the version of Python you want to use when executing your script. As for conda VS venv, it highly depends on your goal. You might also want to consider using something like uv that will help you manage your dependencies and environnement. Since you are starting fresh, I would recommend testing uv.

Hi, What does ~file qmake6 return ?

dnf -y update this morning. Skipped: qt5-qtbase-5.15.15-1.fc40.x86_64 qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64

Disabling the precompile headers by using the option "-no-pch" resolved this issue.

Fortunately it seems that this bug has been fixed in Qt version 6.8.0

Just comment the line. It worked for me.

@jsulm SURE I will, thanks a lot...