@mpyne said in How to use KDE Frameworks with Qt Creator:

Hi @daljit97, as you guessed, the difficulty is in helping Qt to find the appropriate metadata so that qmake knows how to handle "KSyntaxHighlighting" when it finds it in your QMake project file.

Looking at some of the Qt docs on a related topic, I found this page on advanced QMake usage.

The part you care about is the third option to add features to qmake: using the QMAKEPATH environment variable. By exporting this variable in your shell to the KF5 install directory, qmake should be able to find the various KF5 modules.

For example, my KF5 install is at ~/kde-5, so I did something like:

export QMAKEPATH=$HOME/kde-5 qmake make

on a shell project

# program.pro TEMPLATE = app TARGET = program INCLUDEPATH += . QT += widgets KSyntaxHighlighting SOURCES += main.cpp // main.cpp #include <QMainWindow> #include <QApplication> #include <QLabel> #include <Definition> int main(int argc, char **argv) { QApplication app(argc, argv); QMainWindow *win = new QMainWindow; KSyntaxHighlighting::Definition def; win->setCentralWidget( new QLabel(QStringLiteral("Hi!"), win) ); win->show(); return app.exec(); }

It is also possible to build Qt applications with CMake, and that is more traditional for significant KF5 users. But as long as this works for you it looks like it won't be too hard to do what you're trying to do while continuing to use qmake.

Ok so that was very helpful. On my machine that KSyntaxHighlighting had a .pri file in /usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules. Following your suggestion I added a QMAKEPATH Environment variable in Qt Creator using the GUI tool that Qt Creator provides and now everything works!

@J.Hilk Hey, Thank you for all of your help. Solved the problem thanks to you!

If there is anyone facing the same issue, solved like this,
Created a source file named "restarter"
restarter.h

#ifndef RESTARTER_H #define RESTARTER_H #include <QObject> class Restarter : public QObject { Q_OBJECT public: explicit Restarter(QObject *parent = nullptr); Q_INVOKABLE void makeRestart(); signals: public slots: }; #endif // RESTARTER_H

restarter.cpp (note: my application works as a service named "myservice" on system, so I can not restart it as restarting a regular application.)

#include "restarter.h" #include <QProcess> Restarter::Restarter(QObject *parent) : QObject (parent) { } void Restarter::makeRestart() { QProcess::execute("sudo service myservice restart"); }

If your application works NOT AS A SERVICE, BUT AN APPLICATION,
restarter.cpp

#include "restarter.h" #include <QApplication> #include <QProcess> Restarter::Restarter(QObject *parent) : QObject (parent) { } void Restarter::makeRestart() { qApp->quit(); QProcess::startDetached(qApp->arguments()[0], qApp->arguments()); //application restart }

You need to register "restarter.cpp" as a QML registery (I know, stupid sentence)
So you need to insert these lines in main.cpp

#include "restarter.h" qmlRegisterType<Restarter>("closx.restarter", 1, 0, "Restarter");

and use it on your QML file:

import closx.restarter 1.0 Restarter { id:restarter } Rectangle{ id: restartbg width: 120 height: 70 radius: 8 color:"black" anchors.centerIn: parent z:344 Text{ anchors.centerIn: parent text:qsTr("Restart") + mytrans.emptyString font.family:GSystem.myriadproita.name font.pixelSize: 18 color: "white" } MouseArea{ anchors.fill: parent onClicked: { restarter.makeRestart() } onPressed: { restartbg.color = "#1c1c1c" } onReleased: { restartbg.color = "black" } } }

Again, thanks to @LeLev and @J-Hilk for everything.

Hi @newbiSoso

There are some modifications in your code which i tried. Rectangle{ id: rect width: 50 height: width color: squareColor radius: 10 } In QML you cant compare color with string as its HEX value
So make these changes. MouseArea{ anchors.fill: parent onClicked: { if (squareColor === "cyan") root.score = root.score + tttt.text; else if (squareColor === "red") root.score = root.score - tttt.text; } } You are doing root.score + tttt.text which will be considered as string concatenation so your score will be something like below image.
I dint get error as you mentioned. but please avoid using string concatenation for int +/- functionality Please use the value from model txt from your code to avoid string concatenation

All the best.

Hi @ivec

Is it normal that I needed to select the compiler manually?

No. but please select the C compiler also.

And how can I enable the use of a debugger to step through my program?

You need to install the Debugging Tools for Windows, included in the Windows SDK. Due to licencing, this is not possible otherwise.

Regards

But... why? Why docker?

Anyway. Do other applications show normally? Like some standard Gnome/KDE apps.

I strongly recommend using something newer than Qt 5.0.1. It was an extremely buggy release. And it's super old.

@aha_1980
That is good news.
Besides getting slower after being patched to death,
i did not experience any freezing.

Hi
You can use
https://doc.qt.io/qt-5/qgraphicsitem.html#qgraphicsitem_cast
and try cast to your child type if it really is, you can then use its members.
so check for NULL and note the docs saying " reimplement the type() function"

@aha_1980
well its not an easy tool to use.

I'm currently fighting with it as well, my antivirus pushes it into quarantine because it may be a potential virus.

Only happens with my own created tools not the QtCreator one.

I'm still trying to figure that one out...

For non Qt code I am trying to call Qcoreapplication with help of another thread.

Here the code:
ApplicationThread.h

#pragma once #include <qthread.h> #include "squidstat_dll_global.h" #include <iostream> class SQUIDSTAT_DLLSHARED_EXPORT ApplicationThread:public QThread { void run(); }; class SQUIDSTAT_DLLSHARED_EXPORT ApplicationStarter : public QObject { Q_OBJECT public: ApplicationStarter(); ~ApplicationStarter(); public slots: void onStarted(); };

ApplicationThread.cpp

#include "ApplicationThread.h" #include "MainWindow.h" #include "qcoreapplication.h" namespace ToolThreadGlobal { static int argc = 1; static char* argv[] = { QString("SquidState.exe").toLocal8Bit().data(),NULL}; static QCoreApplication *coreApp = nullptr; static ApplicationThread *toolThread = nullptr; }; void ApplicationThread::run() { if (ToolThreadGlobal::coreApp){ std::cout << "\nApplicationThread: thread run method is call"; ToolThreadGlobal::coreApp->exec(); } } ApplicationStarter::ApplicationStarter() { if (ToolThreadGlobal::toolThread == nullptr) { std::cout << "\nApplicationstarter Constructor call"; ToolThreadGlobal::toolThread = new ApplicationThread(); connect(ToolThreadGlobal::toolThread, &ApplicationThread::started, this, &ApplicationStarter::onStarted, Qt::DirectConnection); ToolThreadGlobal::toolThread->start(); } } ApplicationStarter::~ApplicationStarter() { std::cout << "\nApplicationStarter:: destructor is called"; // Ensure that the thread and the QCoreApplication are cleanly shut down: ToolThreadGlobal::toolThread->quit(); ToolThreadGlobal::coreApp->quit(); ToolThreadGlobal::coreApp->deleteLater(); ToolThreadGlobal::coreApp = nullptr; ToolThreadGlobal::toolThread->terminate(); ToolThreadGlobal::toolThread->wait(); ToolThreadGlobal::toolThread->deleteLater(); ToolThreadGlobal::toolThread = nullptr; } void ApplicationStarter::onStarted() { std::cout << "\nApplicationStarter::signal received"; if (QCoreApplication::instance() == NULL) { std::cout << "\nApplicationStarter::call QcoreApplication"; ToolThreadGlobal::coreApp = new QCoreApplication(ToolThreadGlobal::argc, ToolThreadGlobal::argv); std::cout << "\nApplicationStarter::call worker"; MainWindow w; std::cout << "\nApplicationStarter::call before exe"; } }

SquidState.h

#pragma once #include "squidstat_dll_global.h" #include "ApplicationThread.h" #ifndef _SQUIDSTAT_H_ #define _SQUIDSTAT_H_ namespace AISquid { class SQUIDSTAT_DLLSHARED_EXPORT SquidStat { public: SquidStat(); ~SquidStat(); void startAPP(); void closeAPP(); }; } #endif // !_SQUIDSTAT_H_

SquidState.cpp

#include <stdlib.h> #include "SquidStat.h" #include "ApplicationThread.h" AISquid::SquidStat::SquidStat() { std::cout << "\nSquidStat: SquidStat class object is created"; }; AISquid::SquidStat::~SquidStat() { std::cout << "\nSquidStat: SquidStat class object is destriod "; }; void AISquid::SquidStat::startAPP() { }; void AISquid::SquidStat::closeAPP() { };

Testing My dll with help of below code.

tester.cpp

#include "SquidStat.h" #include "ApplicationThread.h" void main(int argc, char *argv[]) { ApplicationStarter start; AISquid::SquidStat obj; obj.startAPP(); return; }

OutPut of Tester:

What is wrong am I doing here? I am receiving call for slot onStarted(); once ApplicationStarter start; object is destroy.

Any suggestion would be more appreciable.

@jsulm ok, I didn't pay attention to that.

So I switched to minGW build and GDB works as expected.
Thanks a lot

@Quentin91 said in Qt Creator with MSVC2010 : no valid kit found:

The problem is that I can't download anything as I want as I work in a company

Then how you did you download Qt source code?

If online installer doesn't work you can use the offline installer.

@Rameshwar

@J-Hilk has given you the necessary code to start from. That's why people type in answers to questions. First try that and verify it works.

Then change it so that it writes on your mainwindow or whatever you want instead.

Only after that, write back if you can't get what you want working.

@Eager This solution worked for me thanks!

Hallo.

Wenn Du ausschließlich Qt Widgets benutzen möchtest, so würde
ich vorschlagen, dass Du, z.Bsp., Dein Hauptfenster zwei teilst:
Das eine Unterfenster soll dann die wechselnden Ansichten zeigen, und das andere Unterfenster enthält dann Dein TreeWidget.

Klickt man dann ein Item des TreeWidgets an, wechselt sich die Ansicht im Nebenfenster.

@sirop Vielen Dank für den Tipp.

Ich habe jetzt herausgefunden das DLLs gefehlt haben. Dies habe ich herausgefunden als ich selbst die Anwendung ohne IDE gestartet habe. Da kamen entsprechende Fehlermeldungen. Nach einfügen dieser fehlenden DLLs funktioniert es nun.

Vielen Dank für die Hilfe und an alle ein schönes Wochenende und einen guten Start in die neue Woche.

Grüße
Sven

Vielen Dank @J-Hilk für den Link zur sehr guten Dokumentation was mir weitergeholfen hat.

Vielen Dank auch an @mrjj der auch einen entscheidenen Tipp gegeben hat eben dass es nur mit dem MSVC Compiler funktioniert. Habe beim Installationsprozess von "webengine" auf der rechte Seite gesehen das MSVC 2017 erforderlich ist von daher stimmt die Aussage absolut.

Vielen Vielen Dank nochmals an euch beiden die mir geholfen haben.

Grüße
Sven

Hi Patrick. I'm in the same situation. Installation on archlinux using the official qt5.13 online installer. Android and desktop kits are well configured on qtcreator just by using their respectif qmake. However when I choose the one.of webassembly (wasm_32) distributed by qt, qtcreator warns about the ABI, saying that it is not defined. Its value is unknown-unknown-unknown-.....

I compiled a simple qt project using wasm_32 kit but link fails with the following error main.o: architecture machine must be wasm32.

Any help?

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

This address is rather suspicious. Please tell me you don't have global QWidgets?

No, I have only a dll with function

extern "C" CORE_SHARED_API QMainWindow * svCreateMainWindow() { return new MainWindow; }

(CORE_SHARED_API is __declspec(dllexport))

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

Btw, 0xc0000409 is stack overflow, so be on the lookout for endless recursion.

As I said, QWindowsGuiEventDispatcher::processEvents() is called twice, and I believe those calls are on the same stack level (crush happens in the second call).

@SGaist
Indeed he is
   but if you feed him bugs
after midnight then he goes like

but then you find the actual reason
   for all your problems and then you
feel like

:)

@VRonin Thanks dear. Your link helped me alot.

@Galbarad so please move this topic to SOLVED state.

Strange behavior, nevertheless.

Hi @aha_1980 ,

If you refer to the Clang Code Model Annotations that are also visible in the editor, then no.

Yeah, I referred to this one. It would be nice if Qt Creators supports this.

I try to do set up a complete build to get the compiler output. Thanks!

@DSpider great! please don't forget to mark your post as solved. Thanks.

As I said earlier, very difficult to get the status ethernet using UDP. UDP is fire & forget protocol. You need to build your own mechanism to monitor the status. It could be simple TCP connection to see if the connection alive with remote server. If not you need to get the interfaces status periodically through QNetworkInterface & check if the interface is up. You can use QNetworkInterface::flags() & QNetworkInterface::IsUp to check the status.

@A123 said in New Errors when moving C++ code to QT Creator:

its been used by others for years and it worked perfectly AFAIK with gcc and clang before I started using qtcreator which complained.

Here's my guess: Previously, the assert() macro was disabled. This caused the illegal code to be effectively "commented out", so the compiler didn't detect it. After the migration, the assert() macro was no longer disabled, so the compiler now sees the bad code and (correctly) complains.

See http://www.cplusplus.com/reference/cassert/assert/. You could make your code work again by defining the NDEBUG macro, but be careful: This will disable all assert()s which might cause other errors to go undetected.

P.S. The compiler is the one that complained, not Qt Creator.

@jsmolka said in Trouble compiling files with identical filenames:

Is there any way to fix that and use multiple files with the same name inside my Qt project? Does it perhaps have something to do with the fact, that I am compiling into a bin dir inside my repository?

Not with shadow building, no. When you generate a bunch of object files in the same directory, the object is named after the source file. So the identically named source's object file will overwrite the previous one (in order of building); it may even happen only partially if you're building on multiple cores.
It's a known pitfall and you should name your files better as people have already suggested.

Define your variables via cpp.defines and use from C++.

@skylendar

you shortened the log, so I can't see the GDB version. Please check these.

Also, GDB must be python enabled, and last the python dumper script must be loaded. Have you checked the directories?

Regards

Another way is to create .dmg file by hdiutil create instead of macdeployqt -dmg .

mkdir ui-release cd ui-release ln -s /Applications cd .. mv $appfolder ui-release/ hdiutil create -volname $volname -srcfolder ui-release/ -ov -format UDZO $dmgfilename

Thank you so much for your helping

@aha_1980 : I just noticed something else: In the log file, there are lines saying "GDB 71101", presumably because it is using v7.11.1 (?!). But I have installed GDB v8.2 in both usr/bin and usr/local/bin. And I've set those locations in QtCreator's options pages for kits and for debuggers. There should be no way for QtCreator to find an older GDB version.

The GDB version in both usr/ folders above is 8.2, confirmed by running via terminal. And I did not find any older stray 7.11.1 versions that QtCreator could be picking up.

Another oddity. Is there any other options page where the GDB location needs to be set?

@Christian-Ehrlicher Thankyou It's Working