Qt 6

@jsulm ok thank you for the help. Indeed grateful.

@cristian-adam Thanks Cristian! I'll check this out.... ✌️

@Ash-V Hi, index is set to -5, model is set to {}, which means it's an empty, default constructed model. Regardless if overridden or not, modelneither has a name, nor a typeproperty. So I don't quite see the problem here. Which value would you expect the properties to have?

@Dilabun I had not looked closely at your code, but what @Ketan__Patel__0011 has written is certainly correct. If that is really the code you have been trying you have created two quite separate QAudioOutputs. The one in audioOutput whose volume you set is not the one which is player's output. So start by sorting that out!

@marisol Looks like gradle version mismatch. Read the links in my post above carefully and try to use the right versions for all packages.

You can try to install new version of Strawberry Perl. Perl is used to generate qmimeprovider_database.cpp as indicated by file "qtbase\src\corelib\mimetypes\mimetypes.pri". mimedb.depends = $$PWD/mime/generate.pl equals(MAKEFILE_GENERATOR, MSVC.NET)|equals(MAKEFILE_GENERATOR, MSBUILD)|isEmpty(QMAKE_SH) { mimedb.commands = cmd /c $$shell_path($$PWD/mime/generate.bat) mimedb.depends += $$PWD/mime/generate.bat $$PWD/mime/hexdump.ps1 } else { mimedb.commands = perl $${mimedb.depends} } Refer to https://www.qtcentre.org/threads/71253-Static-Build-Issue-on-QT-5-15-0?p=309507#post309507 Then, if "qmimeprovider_database.cpp" is generated correctly, the compilation works.

@Dragoner said in qtpropertybrowser with Qt6: -Wa,-mbig-obj (This is ONE compiler flag, so the comma is not a typo!) Correct. Specifically, it says that the compiler should pass the comma-separated list of arguments that follows (-mbig-obj) to the assembler (-Wa), when it gets run. There are also -Wp, flags, to pass arguments to the preprocessor stage, and -Wl, flags, when an option needs to go to the linker. In gcc , at least, the -Xassembler, -Xpreprocessor, and -Xlinker flags can be used to do the same thing one argument at a time, without comma-separating them. (e.g. these are equivalent:) $ gcc -Xassembler -mbig-obj ... $ gcc -Wa,-mbig-obj ...

Hi and welcome to devnet, AFAIK, you can't.

@cristian-adam After spending 6 hours trying to set up OpenCV with Qt6 while following several tutorials (only to find out that it all does not apply to Qt6), your solution worked perfectly fine. I should only add that I struggled with Qt Creator GUI looking for cmake project settings to change CMAKE_PREFIX_PATH. but finally got it (CTRL+5) , Just bookmarked this thread for good. many thanks for this!

@Ash-V Under Linux never type a capital/upper-case letter unless you have a very good reason for doing so.

@JonB That fixed it! Thanks Christian and Jon for your help. Sorry to be such a pain Christian. Rick

This lead to QTBUG-123768

@pedisChen See this post.

@Teemo-of-LOL said: Aren't there two categories: supporting some parts of the C++ standard or supporting it entirely? When it comes to a compiler yes, you could say that. When it comes to a library, like Qt, no, that statement makes no sense. The article you linked is talking about Qt using some features from the C++17 standard and thus requiring a compiler that provides this language version.

@JonB Windows 64 Error : Use of undeclared identifier case AF_INET: inet_ntop(AF_INET, &(((struct sockaddr_in *)sa)->sin_addr), host, salen); break; case AF_INET6: inet_ntop(AF_INET6, &(((struct sockaddr_in6 *)sa)->sin6_addr), host, salen); break;

@Teemo-of-LOL said in I have a question regarding the build process.: When I receive the program on another computer Please explain what exactly you copy to the other machine. Do you also copy the build folder? If so, then do not do that. Only source code is needed to build. Also mentioning what errors you actually get can help to find the problem.

@Teemo-of-LOL maybe because you compiled qt for release version

@JonB Yes exactly.The only thing is that he will have to remove the request headers from the sent packet, and put the original data in a file. In a nutshell, when sending files with upload, the request headers are sent with the file data.You just need to separate both and keep the essential part