I am using Qt 5.15.2 enterprise edition on Windows 10. I am getting following warning messages continuously, though the application is working fine:
warning C4996: 'QNetworkConfiguration': was declared deprecated
While going through the documents, I realized that both QNetworkConfiguration and QNetworkConfigurationManager classes are obsolete, with a remark that these classes should not be used for new coding.
Please let me know what are the alternative classes to be used for the above two classes.
Thanks in advance.
if you follow comments on https://bugreports.qt.io/browse/QTBUG-58946
there's the info that Qt 6.1 supports the reachability in https://doc.qt.io/qt-6/qnetworkinformation.html
Related
Hi I have a debian image on BBB I have already installed QT creator on B^3 but the problem is whenever I try to start a new project in qt creator, couldn't see any option of kit. Infact when i add qmake and compiler path the application throws error.
What can I do to solve the problem. Can i directly get the full pack of SDK from qt.io/download ?
You must compile Qt libraries for your device (BBB) on your own, using specified compiler. You can find more information on this topic, here:
Qt Cross-Compilation Options
As soon as you compile Qt libraries for your device, you must move them to appropriate directories (on your BBB).
First, I would suggest learning to cross-compile, it's much faster & more easily maintained when you want to move to new versions. There's a ton of documentation and community around doing this. Windows & Linux both of which are probably dated, but info is still relavent. I've heard it's much easier from a linux host, but that could be biased.
That being said, if you don't want to cross-compile I believe you can simply install the qt embedded libraries. This question may offer some good advice. Once you have the libraries installed, you should be able to use qmake directly to create the Makefile for your project, then you can use cmake, or g++, etc.. to do the actual compiling.
You're likely going to work in command line though, I'm not sure you can run QT Creator on the BBB directly. I could be wrong.
Where can I find a program which can be executed on Visual studio to compile openGL sources and generate libraries like opengl32.lib, glut32.lib, etc. In fact I have a problem of version with QT. I want to execute opengl using QT but without QT Opengl API.
Here's the error message :
lnk2026 module unsafe for safeseh image opengl32.lib
I'm really lost.
Thanks in advance for your help.
OpenGL is a specification, not a library with a defined source code. OpenGL implementations are what you use, and most of them are propietary. Some of them are open source (such as MESA), but in general you do not have public access to the source code.
The "Open" in "OpenGL" refers to the nature of the specification, not to the concept of "open source". OpenGL is "Open" in that the specification is freely available and can be implemented by anyone (modulo patent claims).
So while you can compile free-standing implementations of OpenGL, what your operating system provides (in your case, via opengl32.lib and opengl32.dll) is not something you can compile yourself.
I've installed Qt SDK 5.0.0 beta 2 and Qt Creator 2.6.0. It detects the package but gives a warning that "No qmlviewer installed". I've looked for it and it is in the SDK bin folder. What can I do? I use ubuntu 12.04 and I've added the SDK binaries to the PATH. I can view the QML files through the terminal.
It is not a solution but maybe it will be helpful.
I can see this warning too, but I think it is not a big problem. I have started to move my existing Quick1 code to new Qt version and I have not seen Qt5 Kit in the drop down list. But when I have created new Quick2 application I found it. And everything seems to work without QMLviewer.
Btw, I found forum post about Qt5 and qmlveiwer. Guy says that it was very difficult to support viewer in the actual state because API of declarative modules are changing very quickly. So they have dropped qmlviewer from Qt5.
I am using Squish 4.2.2 for testing a GUI developed in Qt version 4.7 on linux. The AUT is built using statically linked Qt libraries. Since squish doesnot allow recording for statically linked Qt libraries, I am planning to manually create the test cases. However the squish test case fails with following error
Error Script Error Oct 31, 2012
Detail RuntimeError: startApplication() failed
The test case contains a single line to start the AUT. The server log shows only the following warning
AUT does not appear to be dynamically linked against Qt, hooking might fail.
Has anyone else faced a similar issue when testing Qt applications that are statically linked to Qt libraries? Kindly provide pointers for this issue.
Regards
adj
I have run into this error before and, one of the lessons learned was that the versions of Qt that your application is using
QtCore and QtGui
has to be compatible with the version of Qt squish was compiled with. If they are not, you get this error because squish cannot hook into the application.
You need to have the following correctly setup:
1. The version of Squish must be compatible with the version of Qt used to develop the app. Usually both versions must be the SAME to be compatible.
2. When setting up Squish, point it to the correct QtCore path.
3. Add the application in Edit -> Server Settings -> Manage AUT in the IDE.
I'm trying to make an unsigned sis package of my application, however I get the aforementioned error from QtCreator.
What am I doing wrong?
Best regards
I've got the same problem with Qt 4.6.3. Qt 4.7.3 creates unsigned .sis files without any issues, but 4.6.x doesn't. If the version of Qt isn't important for you, upgrade to 4.7.
I'm looking for another way to solve this, because I want to support old devices that don't work with Qt 4.7
UPD:
I found two ways to create unsigned sis:
Create a signed sis file with QtCreator and remove signature with Syscontents tool
Copy template .pkg, edit it a bit and create sis with makesis commandline tool.
I used the second way, because I use localized installation file. Localized installations work bad in Qt 4.6.3 out of box, so I had to create custom .pkg file
You can't install unsigned application to the phone. Try to sign it and see if it works better