Installation and Deployment

@Mark81 win 7 isn't officially supported for Qt6 So you will have to use modified Qt6 libraries. see @hskoglund 's thread here: https://forum.qt.io/topic/133002/qt-creator-6-0-1-and-qt-6-2-2-running-on-windows-7 for more information on how to do that.

Hi, This looks like a Mac specific flag that might be only available through clang (not sure though). AFAIR, the macx-g++ mkspec (or equivalent for Qt 6) is mainly there for historical reasons, you may have to modify it to build using gcc.

Looks like some css. What is it exactly ?

@amith_r said in Unable to install QT 5.15.2 version on linux 18.04 using latest QT creator. GLIBC_2.28 dependency: Can I know how to run the offline installer for 5.15.2 You download the installer You make it executable (chmod u+x INSTALLER_FILE_NAME) You run it (in terminal: ./INSTALLER_FILE_NAME)

Hi, and welcome! @Tom-Ernst said in How can I deploy from windows to linux ?: My "Qt-building" console is Powershell, configured for using MSVC-dev-environment What you want might be a bit tricky to set up in PowerShell, but the following blog posts should be a good place to start: https://www.qt.io/blog/creating-an-embedded-qt-quick-application-in-visual-studio-1/2 https://www.qt.io/blog/creating-an-embedded-qt-quick-application-in-visual-studio-2/2

Sure you can but that is a separate install. Microsoft does not allow third party installation. As for the deployment, windeployqt is the cousin of macdeployqt. Using it will simplify the deployment process.

Hi and welcome to devnet, I would recommend bringing that question to the KDE people from that project.

Hi, You can't cross-compile from Visual Studio to other OSs. For Androïd, you already have the Qt build and need to install the compilation environment. As for Linux you would need a cross-compiler as well as a cross-compiled Qt build. For macOS, there's nothing non native that you can use. For Linux, you could take advantage of WSL2 to your build though.

@ing-s The next step is just search the missing library -l<library-name> and search through apt command, install the dev package and execute make again: user@user:~/Qt/qtquickdesigner-components$ apt search xkbcommon user@user:~/Qt/qtquickdesigner-components$ sudo apt install libxkbcommon-dev user@user:~/Qt/qtquickdesigner-components$ make user@user:~/Qt/qtquickdesigner-components$ make install And done for anyone who see this.

@hskoglund YES YES YES !!!! I have WEBROOT SecureAnywhere CE22.1 installed . Typically, I run without an internet connection on my machine, so it wasn't vetting any external traffic, ....HOWEVER.... if I disable the "Realtime Shield" option, I am able to launch Qt Creator successfully ON EVERY ATTEMPT TO DO SO! The other enable/disable options on WEBROOT are " Web shield" and "Firewall", both of which are inapplicable to this solution (don't cares). This absolutely seems to resolve my problem! Now, is there a good way to share this information on forum here so others may benefit from this finding? I'm sure others will step into this pile along the way as well. Interesting side note. Both of my Win10 machines that have NOT exhibited the problem are running WEBROOT as well. I'm not sure what is different there, but disabling the Realtime Shield in WEBROOT absolutely resolves my issue on the Win11 machine. Thanks again SO MUCH for your help!

@Wasee Please take time to find out how to build properly. There is INSTALL file in the source archive which points to https://doc.qt.io/archives/qt-4.8/installation.html. There you go to https://doc.qt.io/archives/qt-4.8/install-x11.html and follow the instructions. Why don't you build latest Qt 4.8 release which is 4.8.7?

@Nunzio said in Problems with CANOPEN on arm Cortex: qt 6.2.4 I don't think you're using Qt6. Because Qt6 has the methods and you would not get these errors, see https://doc-snapshots.qt.io/qt6-dev/qcanbusdeviceinfo.html Make sure you really use Qt6.

I didn't expect it. BUT THE NEW INSTALL WORKED JUST FOR THE FIRST TWO PROJECTS. Now it's back to invalid qmake.exe..... [image: IFN7cCXOSKZT.png?o=1] Literrally no more then 24 hours passed and it started doing this again. What is going on? Turns out no matter how many times I install it it does this? [image: DqqR0g0WbYLb.png?o=1] [image: MgDx0mN1tLtE.png?o=1]

I fixed this on my machine by requiring py2app version 0.25 setup_requires=['py2app==0.25'] in the setup.py This problem is described in https://github.com/ronaldoussoren/py2app/issues/380 and there's already a patch. Just don't use 0.26 and 0.27.

Updating SDK helped: https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/

Qt 5 is still more widely used at this time so you will find more information for it. Qt 4 has reached end of life a long time ago, so don't start with it. If memory serves well, the banana pi is close to the Raspberry Pi so this guide might be of interest. Note that is have not tested it.

@bee65 said in Package app as .AppImage after building with Qt Creator: Instead of trying to work out what libraries are needed, I thought I would try just shipping the whole darn lot. I took a copy of the Qt/6.2.3/gcc_64 folder, deleted a bunch of stuff that is not runtime-related, did the chrpath thing, and it seems to work fine. Great thinking, and congrats on your progress! In essence, you have done the Linux version of the "Quick and dirty" deployment described at https://wiki.qt.io/Deploy_an_Application_on_Windows Hopefully this diagram provides a bit of clarity to the deployment process: [image: Qt_Deployment_Structure_Windows.png]