Qt 6

@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

@yass1213 First just verify that C:\Qt2\Tools\mingw1120_64\bin\gcc does indeed exist. i ve added the C:\Qt2\Tools\mingw1120_64\bin\windres.exe to the PATH but in vain the error persestis I trust you mean you added just C:\Qt2\Tools\mingw1120_64\bin to PATH. If nobody here knows/gives you an answer, I suggest you Google for windres.exe: can't popen This error has popped up occasionally over the years --- going back a decade! --- for installations of MinGW. I'm afarid I think you would have to look through these to see if any apply to your situation.

@sierdzio okay. Thank you. I will try. and tell you about result :)

So you did not install Qt6 via the online installer but want to use the one from Ubuntu? Then you also have to install all Qt development packages.

@DeepakVishak SGaist is right. custom GStreamer pipelines have been dropped in Qt 6 Multimedia, however you can achieve the same using qml6glsink. Have a look at this example: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/tree/1.24/subprojects/gst-plugins-good/tests/examples/qt6/qmlsink?ref_type=heads

@Basile_Starynkevitch I don't know what your command is or how you are presently sending it to QProcess as you do not show these. You can normally leave the correct quoting to QProcess with an argument list. If, for some reason, you have a string and want to split it into arguments for QProcess you can use QStringList QProcess::splitCommand(QStringView command). Also void QProcess::startCommand(const QString &command, QIODeviceBase::OpenMode mode = ReadWrite) presumably uses that internally. Note however that you reference https://docs.gtk.org/glib/func.shell_quote.html and that says Quotes a string so that the shell (/bin/sh) will interpret the quoted string to mean unquoted_string. Quoting to a shell like /bin/sh can have its own rules. For example, echo '$HOME' and echo "$HOME" behave differently. I don't know how/whether you deal with that. And your GLib shell_quote ignores this.

@sierdzio I replied to someone else by mistake. I noticed it late. It seems similar to what I found. Link: https://stackoverflow.com/questions/70373606/how-to-fix-qt-requires-a-c17-compiler. Thank you for the detailed explanation. In my case, although I don't encounter errors, it seems I need to reconfigure the C++ standard language setting. Thank you

@Ash-V May I ask: I thought you were a "beginner" at Qt, maybe C++ too (but perhaps not). If you know what you are doing, and have a good usage case, using all the Q_D and d_ptr stuff may be fine. But I, and most people, have never used them, so I just wonder whether you might be over-complicating things.

@Teemo-of-LOL said in Question about Qtftp.: Does the qtftp functionality also come included in Qt5compat? No, QFtp is a separate library. As we already told you, you have to port them by yourself if you need it or use QNetworkAccessManager.

May be this is a window11 system problem. now this problem is disappear

@Christian-Ehrlicher Thank you very much!

Just open the 32 bit MSVC command prompt instead the 64bit one.

@JonB Thank you Jon ! Thanks for giving this additional valuable reply....

@Axel-Spoerl Thanks Axel ! Thank you very much for your valuable reply !

@JonB said in Issues with the new Qt version using the older compiler: I don't know what "imported the old Q5.5.0 compiler into Qt6.6.2" means I expect the latter to be QtCreator. What I find more interesting is the mention of 5.5 That release was tagged June 2015