qmake

What is Qt Bare Metal?

五迷三道 提交于 2019-12-03 14:08:48
QtCreator has a plugin named "Bare Metal". Bare Metal means a computer without an operating system. I have not seen much about Qt Bare Metal development. Is it a way to develop Qt for a bare metal system? Does Qt run on a system with no OS? If yes, what are the advantages of this approach for embedded system development? Is it a way to develop Qt for a bare metal system? No. Does Qt run on a system with no OS? No. Bare Metal means you usually have a few KB of RAM and ROM. I think you are confusing Qt (framework) with QtCreator (IDE). Tim Sander explains it clearly here at the Qt Developer Days

Make qmake use qt5 by default

纵饮孤独 提交于 2019-12-03 13:10:17
I have both qt4 and qt5 on my Linux system. qt4 is used by default. What is a clean way to change that so that qmake uses qmake-qt5 by default? The system might have different meta packages that handle the default. For example on Debian there is a qt4-default and a qt5-default package, installing one of them will uninstall the other and set the symlinks appropriately There is a tool named qtchooser to switch between Qt versions. On Debian and Ubuntu you can install it with apt-get install qtchooser . Easiest way is to use it to list the alternatives and then create QT_SELECT environment

Force QtCreator to run “qmake” when building

て烟熏妆下的殇ゞ 提交于 2019-12-03 12:57:31
问题 In some of my projects I use some pre-build step(s) configured in the .pro file. So qmake will execute this step whenever it is activated. Now in QtCreator, when I build (also when completely rebuilding the whole project), it doesn't always run qmake , since it tries to be clever and optimize this. It only runs it when the .pro file has been changed, causing several issues. Also a common issue is, when you make a class inheriting from QObject after running qmake on that file, it will not

How to specify target mac os x version using qmake

为君一笑 提交于 2019-12-03 12:51:11
问题 I am trying to compile c++11 code on the Mac OS X using Qt Creator/qmake and I am getting the following error: clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) When I checked the compile command line, I noticed that it contains the -mmacosx-version-min=10.6 flag. I tried to update my .pro file as follows, but it seems that this is not taken into account: QMAKE_CXXFLAGS += -std=c++11 -stdlib=libc++ macx { -mmacosx-version-min=10.7 } Any suggestions would

Installing PyQt

那年仲夏 提交于 2019-12-03 12:23:53
问题 I'm trying to install PyQt on my mac so that I can install python ghost. I've already installed Qt, and SIP. I've downloaded PyQt, but when I run python configure-ng.py I get the following error: Error: Use the --qmake argument to explicitly specify a working Qt qmake. Any ideas on what I should do? 回答1: Since you are on a Mac, I would use Homebrew. This worked for me the other day, but took a long time to finish: brew install pyqt 回答2: configure-ng.py needs both qmake and sip to configure

Cannot make new project in QT on mac osx

风格不统一 提交于 2019-12-03 12:15:40
I have been stuck on this for the past couple days. I have installed QT 4.8 and I have installed the libraries as well. But when I come to make a new project, I am only given the option of creating a plain C++ project with CMake. I do not have the option of using the automated qmake. And I have no idea why. If someone could please help it out it would be much appreciated. Here is a picture of what I see. When I see the kits in preferences, I see this. But in the QT versions section, If I click on that to choose something, It is empty. There is nothing to choose from. Add a Qt Version. Go to Qt

Does a Qt 5 programmer have to know about DEPENDPATH qmake variable?

心不动则不痛 提交于 2019-12-03 12:15:17
With Qt 4 you are bound to get in trouble if you do not setup the variable correctly. Sergey Skoblikov If you program with Qt 5 you can safely forget that DEPENDPATH variable exists. All included files will generate dependencies for files in which they are included regardless of directories they reside. You don't have to put up with the variable in Qt 4 too. Just add this to your .pro file: CONFIG += depend_includepath If you want to use DEPENDPATH variable for some reasons with Qt 5 you can switch the option off: CONFIG -= depend_includepath But be aware that DEPENDPATH variable behavior was

Project ERROR: Unknown module(s) in QT: multimedia

爱⌒轻易说出口 提交于 2019-12-03 11:40:22
I am trying to compile qGo , after installing qt5 git clone https://github.com/pzorin/qgo.git cd qgo qmake make sudo make install Right now the latest error is saying it can't find multimedia # make cd src/ && ( test -e Makefile || /usr/lib/x86_64-linux-gnu/qt5/bin/qmake /home/jdm/Downloads/qgo/src/src.pro -o Makefile ) && make -f Makefile Project ERROR: Unknown module(s) in QT: multimedia make: *** [sub-src-make_first] Error 3 I guessed the library libqt5multimedia5 based on this question, but the computer it says its already there and the error persists. libqt5multimedia5 is already the

How to set build order in Qt subdir project

给你一囗甜甜゛ 提交于 2019-12-03 10:14:19
I have a project with 5-6 libraries and one executable. The executable depends on the libraries, and some libraries depend on other libraries. How can I specify a build order so the dependencies are built before they are needed? Although this question has been answered and accepted a long time ago, I feel the need to add another answer; I honestly think that there is a better answer. I consider CONFIG += ordered harmful and a bad habit. It is probably something that was a bit prematurely introduced by the qmake developers. And there are strong opponents to its use. The drawbacks are these: it

How to copy Qt runtime DLLs to project output

寵の児 提交于 2019-12-03 06:36:51
问题 I have a simple project created in Qt Creator (installed using Qt SDK 1.1.4). It runs just fine from within Qt Creator, but if I then browse to the output directory in Windows and double-click the EXE, I'll get an error like: The program can't start because QtCored4.dll is missing from your computer. Try reinstalling the program to fix this problem. That's obviously because Qt isn't in my PATH (and I don't want it to be, in case I have multiple versions of Qt on my computer), and Qt Creator /