@aha_1980 This is exactly, not almost, what I was looking for. Thanks a lot!

@hskoglund said in How to analyze a KIT environment variable: Hi, in a .cpp file you can use getenv(), like this: QString target = getenv("TARGET"); Or qEnvironmentVariable which returns a QString.

@rosetter The bug report is QTCREATORBUG-21258

@aha_1980 The funny thing is the comma. I have just tried and windows 10 you can rename a file to hold a ",v" at the end, but this either part of the extension or part of the filename. In the command prompt this command would generate dir >outfile,v a file outfile without the ",v" (comma vi) at the end. All this makes the behaviour really strange and its use very limited, if there one at all.

gcc: gcc version 6.4.0 20170820 (Debian 6.4.0-4) gdb: GNU gdb 7.11.1 Program code: #include <iostream> using namespace std; int main() { cout << "Hello World!" << endl; return 0; }

Qt Designer is included in Qt sources and works only for UI files. Qt Creator (the IDE) is a separate application and a separate project. You need to install or compile it first, for example from qt.io/downloads. Once you have Qt Creator installer, you need to open the settings, add your Qt Version, then add a so called Kit (which is Qt Version + compiler bundle), and then you are ready to go. If you want to avoid all that hassle, use the Qt installer from the link above - it will install Qt, Qt Creator, and set everything up for you, completely automatically.

I've partialy analysed AutoTest code. For QTest it checks if given source file (after macro preprocesing) has QTest include and QTest::exec() somewhere in code. In my case it lead to usage of TestRunner modified to store function object #define DECLARE_TEST_RUNNER(className) \ namespace { \ int executeTestClass(int argc, char* argv[]) \ { \ className test; \ return QTest::qExec(&test, argc, argv); \ }; \ static char test_##className = \ TestRunner::Instance().RegisterTestClassRunner(executeTestClass); \ } Macro is placed at begining of each CPP file with test details (to decouple as much as possible) However Autotest still acts strangely. Sometimes it discover tests, sometimes not. I believe that it may search in source context of currently selected run target. PS: When I expanded one of DECLARE_TEST_RUNNER macro - AutoTest start displaying green arrows. Not before. Building main exe or ut.exe isn't helping. Calling 'Refresh test' from Tools->Tests also doesn't help. I still don't know what triggers test gathering. PSS: In each test binary at least one QTest::qExec should be expanded out of MACRO. From this point - AutoTest shows also test runners hidden in MACRO and run then all.

I have now. It was not out when I did the original test. Anyway with Creator 4.3.1 it seems to be OK independently from the compiler or Qt version. I guess this solves it. Thanks for pointing out.

It worked! I had done it before but it was adding to the errors, and when I solved those I forgot to re add that. Thanks!

@sierdzio It is the latest version of Qt creator (4.2.1), but unfortunately with the debugging issue for standard containers. I did not manage to install a previous version in addtion, yet. I do not have an SSD yet. Still on the wishlist as basically the whole new machine is. :(

Did some simple tests and unfortunately cannot reproduce with small sample. I have created a default application with QT += core QT -= gui CONFIG += c++11 TARGET = ModeTest CONFIG += console CONFIG -= app_bundle TEMPLATE = app CONFIG(debug, debug|release):TARGET = $$join(TARGET,,,"DebugMode") message("TARGET " $$TARGET) DESTDIR = c:/Source/Utilities SOURCES += main.cpp and #include <QCoreApplication> int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); return a.exec(); } When changing on the left side in creator from debug to release forward and back the name of the exe is always correctly displayed based on chosen on chosen mode. Also the exe can be produced and file sizes are as to be expected. As next I have added a subdirs project which is using the project above. TEMPLATE = subdirs SUBDIRS = ModeTest ModeTest.subdir = ../ModeTest The same. My problem cannot be reproduced easily. Possibly the problem is triggered by other actions in between, but no clue at the moment.

@jsulm Ok, i will makes progress goes on. Thank you very much. Best Regards.

@koahnig said: Either you need to add "-j4" as make parameter to each of your projects. Otherwise you can set also "MAKEFLAGS=-j4" to your environment (e.g. for a kit as suggested above). Correction to above post. I have set it to system environment. I did not get it to work in kit environment. Both were set due to my trials, but the latter alone (in kit environment) does not help.

It is: Qualcomm Snapdragon 805 You should either create another virtual device with x86 CPU or use Qt for Android ARM.

@thosrtanner Hi, and welcome to the Qt forum! Has anyone had any similar problems Best way to find out is to visit the bug tracker and search for QTCREATORBUG.

I'll try that, thanks for the help.

Hi, Did you re-run qmake after changing the DEFINES ?

https://bugreports.qt.io/browse/QTCREATORBUG-16172

Finally, I found the reason. I had to add -Wl,-rpath,$(ROOTSYS)/lib to the end of the LIBS definition. So the solution is the following: Add ROOTSYS to the Projects/Build Environment Add -Wl,-rpath,$(ROOTSYS)/lib to the libs. The .pro file looks like this: TEMPLATE = app win32 { QMAKE_CXXFLAGS += -FIw32pragma.h } CONFIG += qt warn_on thread INCLUDEPATH += $(ROOTSYS)/include win32:LIBS += -L$(ROOTSYS)/lib -llibCore -llibCint -llibRIO -llibNet \ -llibHist -llibGraf -llibGraf3d -llibGpad -llibTree \ -llibRint -llibPostscript -llibMatrix -llibPhysics \ -llibGui -llibRGL else:LIBS += -L$(ROOTSYS)/lib -lCore -lCint -lRIO -lNet \ -lHist -lGraf -lGraf3d -lGpad -lTree \ -lRint -lPostscript -lMatrix -lPhysics \ -lGui -lRGL -Wl,-rpath,$(ROOTSYS)/lib HEADERS += canvas.h SOURCES += canvas.cxx main.cxx

It's not just "yet another app" to learn. It's the current defacto version control system used by Qt, KDE, the linux kernel and many more projects. Even if you're the only developer, that's something you really want to learn to use.

Hi, To add to @mrjj, if you want to add support for the dock icon drop, take a look at QOpenFileEvent There's an example there. Follow the link, the example is not part of Qt 5.5's documentation but will be in 5.6

Thanks, worked as expected!

@SGaist You're right. I did not remember the const keyword. However, it would be interesting a dialog for asking which the desired parameter type.

Hi and welcome to devnet, Please take the time to search the forum a bit. This question has been asked and answered many times already (even again in the last 7 days). You are missing the OpenGL dev libraries. apt-get install libgl1-mesa-dev

I'll answer my own question, kinda. Ctrl+Space and C-x,C-x were a misunderstanding on my part. As for Ctrl+Home/End, I don't know why but building Creator from the master (development) branch solves that problem. So I'll keep my fingers crossed and hope that all is well in the next version.

Qt i debugger to 2 różne rzeczy. Nie zaśmiecaj PATH. Dodawanie tam Qt nic nie da a może sporo popsuć. Którego IDE używasz - Qt Creator czy Visual Studio? Jesli Qt Creator to który kompilator - MinGW czy kompilator z Visual Studio? Jeśli MinGW to gdb (debugger) powinien być zainstalowany razem z nim i ustawiony automatycznie. Żeby zainstalowac debugger dla VS trzeba zaznaczyc opcję "Debugging tools for Windows" instalując Windows SDK. Napisałeś że zainstalowałeś całe, ale upewnij się - sprawdź, czy w ścieżce <ścieżka do Windows SDK>/Debuggers/x64/ jest plik cdb.exe (plik debuggera). Jesli nie to pewnie ominąłeś ten checkbox w instalatorze. Sprawdź, czy Qt Creator widzi debugger - Tools -> Options -> Build & Run -> Debuggers: powinieneś tam widzieć coś w rodzaju "Auto-detected CDB at ...". Sprawdź, czy twój kit ma ustawiony debugger (pewnie nie jesli doinstalowałeś go potem. Wejdź do Tools -> options -> Build & Run -> Kits, zaznac swój kit i zobacz czy ma usatwiony debugger. Jesli nie to wybierz CDB z listy.

@jsulm I add a button even as below. void Dialog::on_pushButton_clicked() { SubView *QQ=new SubView(this); QQ->setModal(true); QQ->setEnabled(true); QQ->showNormal(); } Then, I put a QEditline on the subview . Of course, subview is a class inherited from the dialog. This is a very simple code. Or You can try this https://github.com/mkdh/QEditlineOnNewWidgetiOS

Did you try setting antyaliassing? http://doc.qt.io/qt-5/qpainter.html#setRenderHint