General and Desktop

This is not a problem. The linguist.exe.debug should be a Release Build with Debug Information, which due to some weird reason gets truncated to 792 bytes (not kilo bytes). linguist.exe is available, which is only the release binary without debugging information. You can safely delete the linguist.exe.debug file and not have to deal with the antivirus complaining of an invalid executable.

Yes...that's it. And I thought I was doing something wrong in the class somewhere! Many thanks!!!

Thank you! I close the topic :)

In order to build Qt Creator plugins you don't need to build Qt Creator itself. Unless you are using a compiler that is not used to build the official Qt Installations. For example, you only need to select the Qt Creator 6.0.2 Plugin Development checkbox in the installer. [image: ba633892-b2c2-47db-b647-c3593a9a2430.png]  If you decide to build Qt Creator yourself, please note that the CMake build system is being officially supported to build Qt Creator.

@Wasee said in How we can add integers?: RX LO:2464999998 2^32 4294967296 int(2^32) -2147483648 int(2464999998) -2147483648 Strange .... [EDIT] INT_MIN Minimum value for a variable of type int . -2147483648 read.toInt(&ok,16); Are you sure your string is in hexa ?

@freenico said in application (Qt Quick) - only 'Desktop' in Supported Platforms: I wonder whats cooking under your statement a couple of things really, LTS and offline installer to become commercial-only Moving core features like TreeView to the QtMarketPlace for additional yearly subscriptions, or GPL Change from subscription to Qt overall, to subscription of individual modules. Would I change over to Qt6 I would have to pay 3 times from what I'm currently paying. "LTS" versions are commercial only now Community bug fixes aren't open sourced until after a year later That said, if you're an open source user of Qt and willing to always update to the latest Qt6 version, absolutely nothing changes for you :D now i see all the things you guys were asking me before 😜 but, I'm not sure why you don't have a "Multi-Abi" android version as well?

@J-Hilk ops! early morning here. I could not see it on the page. thanks

Oh, what a silly mistake! Thank you very much!

Current solution is: from Kits section, from CMake parameters remove CMAKE_PREFIX_PATH ensure that CMAKE_MAKE_PROGRAM leads to host OS make (at least for me - I couldn't find make in native sysroot) exports in environment contained export CXX="arm-poky-linux-gnueabi-g++ -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=$SDKTARGETSYSROOT" and separate CXXFLAGS. Given parameter add to Compiler section, C++ entry, Platform codegen flags wasn't taken under consideration, you need to add it explicit to CXXFLAGS in Kit environment section. At this moment - CMake built successfully C and CXX test and completed project configuration. Project binaries are built and works on target HW. PS: Having working console executed building process for comparison is very helpful.

@ChrisW67 I solved it by removing the focus. setFocusPolicy(Qt::NoFocus);

It's set on the QMediaCaptureSession, isn't it ?

Sure you can, the usual way, subclass and reimplement.

I'm not sure what you're hoping to do in Designer, but if you're trying to auto-size the cells, that's not a Designer function. You'll want to access the QHeaderView of the model you're using to populate the table, using the setStretchLastSection() call.

There are no Qt methods to request this info.

Update: Using the Qt5 solution for accessing the root source tree path works very well. This means that each sub test project has access to the source root directory via a simple variable, ie. $$top_srcdir

@django-Reinhard said in problems with cmake and how I solved it: The point is/was, that cmake interface library definition does only care for the libraries. Not the include directories. This is wrong when you use properly imported targets like Qt provides. Don't know about the other libs though but when they provide imported targets and the proper include dirs are not added then the library creates it's cmake find modules wrong.

I think I've sorted it now. It was an error in the file read loop. Thank you for your assistance.