青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

子彈 の VISIONS

NEVER back down ~~

C++博客 首頁 新隨筆 聯系 聚合 管理
  112 Posts :: 34 Stories :: 99 Comments :: 0 Trackbacks
qmake Project Files

Project files contain all the information required by qmake to build your application, library, or plugin. The resources used by your project are generally specified using a series of declarations, but support for simple programming constructs allow you to describe different build processes for different platforms and environments.

Project File Elements

The project file format used by qmake can be used to support both simple and fairly complex build systems. Simple project files will use a straightforward declarative style, defining standard variables to indicate the source and header files that are used in the project. Complex projects may use the control flow structures to fine-tune the build process.

The following sections describe the different types of elements used in project files.

Variables

In a project file, variables are used to hold lists of strings. In the simplest projects, these variables inform qmake about the configuration options to use, or supply filenames and paths to use in the build process.

qmake looks for certain variables in each project file, and it uses the contents of these to determine what it should write to a Makefile. For example, the list of values in the HEADERS and SOURCES variables are used to tell qmake about header and source files in the same directory as the project file.

Variables can also be used internally to store temporary lists of values, and existing lists of values can be overwritten or extended with new values.

The following lines show how lists of values are assigned to variables:

 HEADERS = mainwindow.h paintwidget.h 

Note that the first assignment only includes values that are specified on the same line as the SOURCES variable. The second assignment splits the items across lines by using the \\ character.

The list of values in a variable is extended in the following way:

 SOURCES = main.cpp mainwindow.cpp \
           paintwidget.cpp
 CONFIG += qt 

The CONFIG variable is another special variable that qmake uses when generating a Makefile. It is discussed in the section on general configuration later in this chapter. In the above line, qt is added to the list of existing values contained in CONFIG.

The following table lists the variables that qmake recognizes, and describes what they should contain.

Variable

Contents

CONFIG

General project configuration options.

DESTDIR

The directory in which the executable or binary file will be placed.

FORMS

A list of .ui files to be processed by uic.

HEADERS

A list of filenames of header (.h) files used when building the project.

QT

Qt-specific configuration options.

RESOURCES

A list of resource (.rc) files to be included in the final project. See the The Qt Resource System for more information about these files.

SOURCES

A list of source code files to be used when building the project.

TEMPLATE

The template to use for the project. This determines whether the output of the build process will be an application, a library, or a plugin.

The contents of a variable can be read by prepending the variable name with $$. This can be used to assign the contents of one variable to another:

 TEMP_SOURCES = $$SOURCES 

The $$ operator is used extensively with built-in functions that operate on strings and lists of values. These are described in the chapter on qmake Advanced Usage.

Normally, variables are used to contain whitespace-separated lists of values. However, it is sometimes necessary to specify values containing spaces. These must be quoted in the following way:

 DEST = "Program Files" 

The quoted text is treated as a single item in the list of values held by the variable.

Comments

You can add comments to project files. Comments begin with the # character and continue to the end of the same line. For example:

 # Comments usually start at the beginning of a line, but they
 # can also follow other content on the same line. 

To include the # character in variable assignments, it is necessary to use the contents of the built-in LITERAL_HASH variable. See the variable reference for more information.

Built-in Functions and Control Flow

qmake provides a number of built-in functions to allow the contents of variables to be processed. The most commonly used function in simple project files is the include function which takes a filename as an argument. The contents of the given file are included in the project file at the place where the include function is used. The include function is most commonly used to include other project files:

 include(other.pro) 

Support for conditional structures is made available via scopes that behave like if statements in programming languages:

 win32 {
     SOURCES += paintwidget_win.cpp
 } 

The assignments inside the braces are only made if the condition is true. In this case, the special win32 variable must be set; this happens automatically on Windows, but this can also be specified on other platforms by running qmake with the -win32 command line option (see Running qmake for more information). The opening brace must stand on the same line as the condition.

Simple loops are constructed by iterating over lists of values using the built-in for function. The following code adds directories to the SUBDIRS variable, but only if they exist:

 EXTRAS = handlers tests docs
 for(dir, EXTRAS) {
     exists($$dir) {
         SUBDIRS += $$dir
     }
 } 

More complex operations on variables that would usually require loops are provided by built-in functions such as find, unique, and count. These functions, and many others are provided to manipulate strings and paths, support user input, and call external tools. A list of the functions available can be found in the qmake Advanced Usage chapter of this manual.

Project Templates

The TEMPLATE variable is used to define the type of project that will be built. If this is not declared in the project file, qmake assumes that an application should be built, and will generate an appropriate Makefile (or equivalent file) for the purpose.

The types of project available are listed in the following table with information about the files that qmake will generate for each of them:

Template

Description of qmake output

app (default)

Creates a Makefile to build an application.

lib

Creates a Makefile to build a library.

subdirs

Creates a Makefile containing rules for the subdirectories specified using the SUBDIRS variable. Each subdirectory must contain its own project file.

vcapp

Creates a Visual Studio Project file to build an application.

vclib

Creates a Visual Studio Project file to build a library.

See the qmake Tutorial for advice on writing project files for projects that use the app and lib templates.

When the subdirs template is used, qmake generates a Makefile to examine each specified subdirectory, process any project file it finds there, and run the platform's make tool on the newly-created Makefile. The SUBDIRS variable is used to contain a list of all the subdirectories to be processed.

General Configuration

The CONFIG variable specifies the options and features that the compiler should use and the libraries that should be linked against. Anything can be added to the CONFIG variable, but the options covered below are recognized by qmake internally.

The following options control the compiler flags that are used to build the project:

Option

Description

release

The project is to be built in release mode. This is ignored if debug is also specified.

debug

The project is to be built in debug mode.

debug_and_release

The project is built in both debug and release modes.

build_all

If debug_and_release is specified, the project is built in both debug and release modes by default.

ordered

When using the subdirs template, this option specifies that the directories listed should be processed in the order in which they are given.

warn_on

The compiler should output as many warnings as possible. This is ignored if warn_off is specified.

warn_off

The compiler should output as few warnings as possible.

The debug_and_release option is special in that it enables both debug and release versions of a project to be built. In such a case, the Makefile that qmake generates includes a rule that builds both versions, and this can be invoked in the following way:

 make all 

Adding the build_all option to the CONFIG variable makes this rule the default when building the project, and installation targets will be created for both debug and release builds.

Note that each of the options specified in the CONFIG variable can also be used as a scope condition. You can test for the presence of certain configuration options by using the built-in CONFIG() function. For example, the following lines show the function as the condition in a scope to test whether only the opengl option is in use:

 CONFIG(opengl) {
     message(Building with OpenGL support.)
 } else {
     message(OpenGL support is not available.)
 } 

This enables different configurations to be defined for release and debug builds, and is described in more detail in the Scopes section of the Advanced Usage chapter of this manual.

The following options define the type of project to be built. Note that some of these options only take effect when used on the relevant platform. On other platforms, they have no effect.

Option

Description

qt

The project is a Qt application and should link against the Qt library. You can use the QT variable to control any additional Qt modules that are required by your application.

thread

The project is a multi-threaded application.

x11

The project is an X11 application or library.

When using application or library project templates, more specialized configuration options can be used to fine tune the build process. These are explained in details in the Common Projects chapter of this manual.

For example, if your application uses the Qt library and you want to build it as a multi-threaded application in debug mode, your project file will contain the following line:

 CONFIG += qt thread debug 

Note, that you must use "+=", not "=", or qmake will not be able to use Qt's configuration to determine the settings needed for your project.

Declaring Qt Libraries

If the CONFIG variable contains the qt value, qmake's support for Qt applications is enabled. This makes it possible to fine-tune which of the Qt modules are used by your application. This is achieved with the QT variable which can be used to declare the required extension modules. For example, we can enable the XML and network modules in the following way:

 CONFIG += qt
 QT += network xml 

Note that QT includes the core and gui modules by default, so the above declaration adds the network and XML modules to this default list. The following assignment omits the default modules, and will lead to errors when the application's source code is being compiled:

 QT = network xml # This will omit the core and gui modules. 

If you want to build a project without the gui module, you need to exclude it with the "-=" operator. By default, QT contains both core and gui, so the following line will result in a minimal Qt project being built:

 QT -= gui # Only the core module is used. 

The table below shows the options that can be used with the QT variable and the features that are associated with each of them:

Option

Features

core (included by default)

QtCore module

gui (included by default)

QtGui module

network

QtNetwork module

opengl

QtOpenGL module

sql

QtSql module

svg

QtSvg module

xml

QtXml module

qt3support

Qt3Support module

Note that adding the opengl option to the QT variable automatically causes the equivalent option to be added to the CONFIG variable. Therefore, for Qt applications, it is not necessary to add the opengl option to both CONFIG and QT.

Configuration Features

qmake can be set up with extra configuration features that are specified in feature (.prf) files. These extra features often provide support for custom tools that are used during the build process. To add a feature to the build process, append the feature name (the stem of the feature filename) to the CONFIG variable.

For example, qmake can configure the build process to take advantage of external libraries that are supported by pkg-config, such as the D-Bus and ogg libraries, with the following lines:

 CONFIG += link_pkgconfig
 PKGCONFIG += ogg dbus-1 

More information about features can be found in the Adding New Configuration Features section of the qmake Advanced Usage chapter.

Declaring Other Libraries

If you are using other libraries in your project in addition to those supplied with Qt, you need to specify them in your project file.

The paths that qmake searches for libraries and the specific libraries to link against can be added to the list of values in the LIBS variable. The paths to the libraries themselves can be given, or the familiar Unix-style notation for specifying libraries and paths can be used if preferred.

For example, the following lines show how a library can be specified:

 LIBS += -L/usr/local/lib -lmath 

The paths containing header files can also be specified in a similar way using the INCLUDEPATH variable.

For example, it is possible to add several paths to be searched for header files:

 INCLUDEPATH = c:/msdev/include d:/stl/include 

[Previous: Using qmake] [Contents] [Next: Running qmake]


Copyright © 2008 Trolltech

Trademarks

Qt 4.3.4

posted on 2008-08-04 12:00 子彈のVISIONS 閱讀(1664) 評論(2)  編輯 收藏 引用 所屬分類: 2.0 工作參考

Feedback

# re: qmake Project Files (.pro) 2008-08-04 12:08 子彈
 
QT中.pro文件的寫法
2008-04-01 15:03
在QT中,有一個工具qmake可以生成一個makefile文件,它是由.pro文件生成而來的,.pro文件的寫法如下:

1. 注釋
從“#”開始,到這一行結束。

2. 指定源文件
SOURCES = *.cpp

對于多源文件,可用空格分開,如:SOURCES = 1.cpp 2.cpp 3.cpp
或者每一個文件可以被列在一個分開的行里面,通過反斜線另起一行,就像這樣:

SOURCES = hello.cpp \
      main.cpp
一個更冗長的方法是單獨地列出每一個文件,就像這樣:

    SOURCES += hello.cpp
    SOURCES += main.cpp

這種方法中使用“+=”比“=”更安全,因為它只是向已有的列表中添加新的文件,而不是替換整個列表。

3. 指定頭文件
HEADERS = hello.h或者HEADERS += hello.h

列出源文件的任何一個方法對頭文件也都適用。

4. 配置信息
CONFIG用來告訴qmake關于應用程序的配置信息。

    CONFIG += qt warn_on release

在這里使用“+=”,是因為我們添加我們的配置選項到任何一個已經存在中。這樣做比使用“=”那樣替換已經指定的所有選項是更安全的。
A> qt部分告訴qmake這個應用程序是使用Qt來連編的。這也就是說qmake在連接和為編譯添加所需的包含路徑的時候會考慮到Qt庫的。
B> warn_on部分告訴qmake要把編譯器設置為輸出警告信息的。
C> release部分告訴qmake應用程序必須被連編為一個發布的應用程序。在開發過程中,程序員也可以使用debug來替換release

5. 指定目標文件名
TARGET = filename

如果不設置該項目,目標名會被自動設置為跟項目文件一樣的名稱

6. 添加界面文件(ui)
INTERFACES = filename.ui

7. 平臺相關性處理
我們在這里需要做的是根據qmake所運行的平臺來使用相應的作用域來進行處理。為Windows平臺添加的依賴平臺的文件的簡單的作用域看起來就像這樣:

win32 {
SOURCES += hello_win.cpp
}

所以如果qmake運行在Windows上的時候,它就會把hello_win.cpp添加到源文件列表中。如果qmake運行在其它平臺上的時候,它會很簡單地把這部分忽略。

8. 如果一個文件不存在,停止qmake
如 果某一個文件不存在的時候,你也許不想生成一個Makefile。我們可以通過使用exists()函數來檢查一個文件是否存在。我們可以通過使用 error()函數把正在運行的qmake停下來。這和作用域的工作方式一樣。只要很簡單地用這個函數來替換作用域條件。對main.cpp文件的檢查就 像這樣:

!exists( main.cpp ) {
   error( "No main.cpp file found" )
}

“!”用來否定這個測試,比如,如果文件存在,exists( main.cpp )是真,如果文件不存在,!exists( main.cpp )是真。

9. 檢查多于一個的條件
假 設你使用Windows并且當你在命令行運行你的應用程序的時候你想能夠看到qDebug()語句。除非你在連編你的程序的時候使用console設置, 你不會看到輸出。我們可以很容易地把console添加到CONFIG行中,這樣在Windows下,Makefile就會有這個設置。但是如果告訴你我 們只是想在當我們的應用程序運行在Windows下并且當debug已經在CONFIG行中的時候,添加console。這需要兩個嵌套的作用域;只要生 成一個作用域,然后在它里面再生成另一個。把設置放在最里面的作用域里,就像這樣:

win32 {
   debug {
     CONFIG += console
   }
}

嵌套的作用域可以使用冒號連接起來,像這樣:

win32:debug {
CONFIG += console
}

10. 摸板
模板變量告訴qmake為這個應用程序生成哪種makefile。下面是可供使用的選擇:

A> app - 建立一個應用程序的makefile。這是默認值,所以如果模板沒有被指定,這個將被使用。
B> lib - 建立一個庫的makefile。
C> vcapp - 建立一個應用程序的Visual Studio項目文件。
D> vclib - 建立一個庫的Visual Studio項目文件。
E> subdirs - 這是一個特殊的模板,它可以創建一個能夠進入特定目錄并且為一個項目文件生成makefile并且為它調用make的makefile。

11. 生成Makefile
當你已經創建好你的項目文件,生成Makefile就很容易了,你所要做的就是先到你所生成的項目文件那里然后輸入:

Makefile可以像這樣由“.pro”文件生成:

    qmake -o Makefile hello.pro

對于Visual Studio的用戶,qmake也可以生成“.dsp”文件,例如:

    qmake -t vcapp -o hello.dsp hello.pro
  回復  更多評論
  

# re: qmake Project Files (.pro) 2010-08-05 14:14 cosplay
I love your blog so much, and there are just some differences with others'. Hope there will be more wonderful things in your blog. .Happy every day!DXFD  回復  更多評論
  

青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            国产精品国产成人国产三级| 亚洲国产综合在线| 亚洲大胆人体视频| 一区二区高清视频| 久久人人97超碰精品888| 久久久免费精品视频| 亚洲天堂视频在线观看| 欧美亚洲第一页| 午夜免费久久久久| 校园激情久久| 国产在线视频不卡二| 久久亚洲精品网站| 久久久久女教师免费一区| 在线观看国产欧美| 欧美成人a视频| 蜜臀久久99精品久久久画质超高清| 亚洲国产精品va在看黑人| 免费看黄裸体一级大秀欧美| 欧美成人激情在线| 正在播放日韩| 亚洲综合二区| 在线观看日韩www视频免费| 国产欧美日韩在线视频| 欧美一站二站| 久久久久久久久岛国免费| 亚洲黄一区二区| 99国产精品99久久久久久| 国产精品最新自拍| 蜜月aⅴ免费一区二区三区| 欧美在线视频一区| 国产一区二区黄色| 欧美激情一区在线| 国产精品大片免费观看| 久久亚洲精品视频| 欧美三级日本三级少妇99| 久久av免费一区| 欧美阿v一级看视频| 亚洲一区二区三区精品在线 | 欧美诱惑福利视频| 亚洲欧美精品伊人久久| 亚洲国产高清高潮精品美女| 亚洲美女性视频| 狠狠色丁香久久婷婷综合丁香| 亚洲狠狠丁香婷婷综合久久久| 国产喷白浆一区二区三区| 男同欧美伦乱| 国产精品视频一区二区三区 | 久久爱www久久做| 亚洲精品乱码久久久久久蜜桃91| 亚洲欧美久久久久一区二区三区| 亚洲国内精品在线| 午夜精品久久| 一区二区三区四区国产精品| 久久久久久久91| 欧美大片一区二区三区| 欧美在线观看日本一区| 欧美日韩成人| 亚洲大片精品永久免费| 国产一区二区丝袜高跟鞋图片| 日韩视频一区二区三区在线播放 | 久久亚洲精品一区| 亚洲毛片网站| 久久免费99精品久久久久久| 一卡二卡3卡四卡高清精品视频| 久久国产精品99国产| 亚洲欧美日韩精品久久亚洲区| 欧美国产日韩xxxxx| 久久国产精品久久久久久久久久| 国产精品国产三级国产专播品爱网 | 久久在线免费观看| 国产日韩欧美三区| 亚洲性人人天天夜夜摸| 亚洲国产精品嫩草影院| 香蕉成人伊视频在线观看| 亚洲综合三区| 国产精品家庭影院| 一区二区三区日韩欧美| 亚洲在线观看免费| 国产精品久久9| 亚洲午夜av在线| 亚洲女女女同性video| 欧美视频一区二区三区| 一本久久综合| 亚洲中字黄色| 亚洲精品资源美女情侣酒店| 亚洲激情影视| 欧美精品网站| 日韩亚洲国产欧美| 亚洲尤物影院| 国产日韩精品一区二区| 亚洲一区日韩| 久久精品女人| **性色生活片久久毛片| 久热国产精品| 亚洲人成网站在线观看播放| 一本色道久久综合一区| 国产精品福利网站| 亚洲一区免费观看| 久久久亚洲欧洲日产国码αv | 欧美精品在线视频| 99精品免费视频| 欧美激情第4页| 男同欧美伦乱| 亚洲一区二区三区在线| 国际精品欧美精品| 欧美承认网站| 亚洲视频一二三| 老司机午夜精品视频| 99精品久久免费看蜜臀剧情介绍| 欧美日韩一区在线视频| 久久成人这里只有精品| 欧美va天堂在线| 亚洲精品一区二区三区av| 欧美福利小视频| 亚洲综合色网站| 欧美国产专区| 亚洲欧美中文在线视频| 1000部精品久久久久久久久| 欧美三级午夜理伦三级中文幕| 久久爱91午夜羞羞| 99www免费人成精品| 久久影院亚洲| 久久国产精品第一页| 99热免费精品| 久久亚洲高清| 一区二区日韩精品| 樱桃国产成人精品视频| 国产精品成人一区二区网站软件| 老妇喷水一区二区三区| 亚洲欧美另类综合偷拍| 亚洲日本无吗高清不卡| 久久偷看各类wc女厕嘘嘘偷窃| 亚洲午夜伦理| 日韩视频第一页| 在线成人h网| 欧美日韩三级视频| 久久激情综合网| 亚洲嫩草精品久久| 一本色道久久加勒比88综合| 欧美成人第一页| 久久久噜久噜久久综合| 欧美一区二区三区免费在线看 | 久久精品理论片| 亚洲欧美清纯在线制服| 一区二区欧美在线观看| 亚洲精品一区在线观看| 在线日韩欧美| 国产精品久久久久9999高清| 欧美日韩国产一级片| 欧美巨乳波霸| 欧美另类一区| 欧美91视频| 免费观看成人www动漫视频| 亚洲欧美国产制服动漫| 国产精品99久久久久久www| 日韩午夜免费视频| 日韩视频免费观看| 999在线观看精品免费不卡网站| 亚洲国产高清一区| 亚洲国产精品一区二区第四页av | 日韩视频一区二区三区| 久久久91精品国产一区二区精品| 午夜亚洲性色福利视频| 午夜精品国产更新| 久久精品国产久精国产一老狼| 国产精品欧美风情| 欧美精品久久久久a| 国产精品av久久久久久麻豆网| 国产精品高清一区二区三区| 国产亚洲美州欧州综合国| 亚洲高清不卡在线观看| 一二三区精品| 久久久久久久久久看片| 亚洲福利国产| 亚洲天堂免费在线观看视频| 久久这里有精品视频| 欧美日韩一区二区三区四区在线观看| 国产精品热久久久久夜色精品三区| 国产在线不卡精品| 中文精品视频| 久久综合九色99| 一区二区三区产品免费精品久久75| 欧美一区二区三区四区夜夜大片| 欧美在线免费| 亚洲经典在线看| 欧美亚洲在线播放| 欧美裸体一区二区三区| 韩国一区电影| 亚洲欧美亚洲| 亚洲精品在线免费观看视频| 欧美在线影院| 国产精品毛片| 日韩视频一区| 欧美 亚欧 日韩视频在线| 亚洲视频在线观看一区| 欧美大香线蕉线伊人久久国产精品| 国产日韩精品一区二区三区在线| 一本大道久久a久久精二百| 老**午夜毛片一区二区三区| 亚洲一区日韩|