asp.net barcode generator Managing Resources with QMake in Font

Printer Data Matrix in Font Managing Resources with QMake

When embedding resources into the executables, you create a resource file that you refer to from the project file. A resource can be an icon, a translation, or any other file that your application uses. (Refer to 4 for more on the resource file format.)

The resource files usually have the file name extension qrc. They are added to the RESOURCES variable in the project file, which causes the resource compiler rcc to compile the specified resources into an intermediate C++ source file. You can control where these intermediate files are placed by using the RCC_DIR variable.

There are several ways to configure Qt during the build process. For instance, you can control what parts of Qt to include and how those parts will behave, which enables you to build your applications to use only the parts of Qt that they need resulting in a smaller executable and smaller memory footprint. You saw some of the defines that can be used to do this in the DEFINES variable discussion, but you will look at more in this section. The two major variables for controlling which parts of Qt to include are QT and CONFIG. QT controls the modules to be included in your project. The default is to include core and gui. The following modules are available (depending on which edition of Qt you are using): core: The core module gui: The user interface module, QtGui, used in all applications having a graphical user interface network: The QtNetwork module, used in 14 opengl: The QtOpenGL module, used in 7 sql: The QtSql module, used in 13 svg: The QtSvg module, used in 7 xml: The QtXml module, used in 8 qt3support: The Qt3Support module, used to make it easier to port Qt 3 applications to Qt 4 The second major variable, the CONFIG variable, is usually set up in a reasonable fashion by default. The most common values to use are the following: thread: If included, the application is built with support for multithreading. console: If included, Windows applications will have a console. This console is used to show qDebug messages, for example. release: Builds the project in release mode. debug: Builds the project in debug mode. debug_and_release: Builds the project in both release and debug modes. plugin: Builds a plugin. dll: Builds a dynamically linkable library, also known as a shared object. qttestlib: Adds the Qt support library for building unit tests.

After you create a project file for your Qt project, you need to run QMake to create the appropriate Makefile or project. The easiest way to do this is to type qmake to a command line interface when in the same directory as the project file. It will use the platform defaults to generate a proper Makefile.

You can also use QMake to generate a project file for Visual Studio. Simply run qmake -t vcapp to generate such a file (replace vcapp with vclib to build a library project). To generate a project file for Xcode, run qmake -spec macx-xcode. You can also add project file lines to your QMake call. For example, qmake "CONFIG+=console" is equivalent to adding the line CONFIG+=console to your project file. If you choose to create a Makefile using QMake, you can build your project using a simple make command (or nmake if you re using Visual Studio). You can clean up your intermediate files using make clean. The slightly more brutal step is to run make distclean, which cleans up all generated files, including the Makefile. You will have to run QMake again to get a Makefile for make.