Hi

For the scalable part.
You must use Layouts from the very start.
https://doc.qt.io/qt-5/layout.html

Hello @alpartis

Thank you for the info. What about import statement of Qt Desing Studio project (in my Qt Creator project)?

import QtQuick import QtQuick.Controls import MyQTDesignStudioProject ###(my project)

I manage to import the ui.qml file but of course, it has the import "MyQTDesignStudioProject" and I get the error:

"Qml module not found (MyQTDesignStudioProject)"
or
"module "MyQTDesignStudioProject" is not installed"

Are there any extra steps I'm missing? (QML_DESIGNER_IMPORT_PATH? Another path?)

Thanks, afalsa

@cube45 said in How to define initial build options with CMakeLists.txt:

How do you publish your app then?

'make install' is your friend.

@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!