blocks|key|2040171|text|如果逻辑和图形用户界面文件夹实际上返回了某种类型的目标，则可以使用subdirs。一个库，可以独立于其他任何东西构建。如果是这样，那么只需使用|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2040172|TEMPLATE+=+lib
TARGET+=+logic
CONFIG+%2B=+dll|code-block|syntax|javascript|2040173|在logic.pro中。|2040174|如果它们不是独立的目标，而只是用来组织源文件的文件夹，那么您可以在每个文件夹中使用一个.pri文件，并使用以下命令将它们包含在.pro中|2040175|include(logic/logic.pri)
include(gui/gui.pri)|2040176|只需记住，.pri文件中的文件路径是相对于.pro文件而不是.pri的。顺便说一句，由于您仍然可以直接在.pro文件中列出这些文件夹中的文件，因此.pri文件的使用是可选的。.pri文件只是让它变得更整洁，并有助于保持.pro文件更短。|2040177|entityMap^0|X|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

You use <code>subdirs</code> if the logic and gui folders actually repesent some sort of target, eg. a library, that can be built independently of anything else. If that's the case then just use

<pre><code>TEMPLATE = lib
TARGET = logic
CONFIG += dll
</code></pre>

in logic.pro.

If they are not independent targets but are just folders that exist to organise the sources files then you can just use a .pri file in each instead and include them within the .pro using

<pre><code>include(logic/logic.pri)
include(gui/gui.pri)
</code></pre>

Just remember that the file paths in the .pri files are relative to the .pro file and not the .pri. BTW, the use of a .pri file is optional as you can still list the files in those folders directly in the .pro file. The .pri file just makes it that bit neater and helps keep the .pro file shorter.

blocks|key|1826373|text|除了Troubadour's+comment之外，我还要注意到SUBDIRS目标只适用于指定子目录。因此，您的额外行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1826374|SOURCES+%2B=+main.cpp|code-block|syntax|javascript|1826375|在您的project.pro文件中是不正确的，并且在最坏的情况下很可能无法构建您的main.cpp文件。在最好的情况下，qmake将拒绝解析该文件，因为它包含冲突的规范。|1826376|我已经用过SUBDIRS模板几次了，如果你能把各个部分构建到或多或少独立的库中，它就能做得很好，就像你把逻辑和gui分开一样。以下是一种方法：|1826377|project_dir/
-project.pro
-common.pri
-logic/
----logic.pro
----some+logic+files
-gui/
----gui.pro
----gui+files
-build/
----build.pro
----main.cpp|1826378|project.pro：|1826379|TEMPLATE+=+subdirs
SUBDIRS+=+logic+\
++++++++++gui

#+build+must+be+last:
CONFIG+%2B=+ordered
SUBDIRS+%2B=+build|1826380|common.pri：|1826381|#Includes+common+configuration+for+all+subdirectory+.pro+files.
INCLUDEPATH+%2B=+.+..
WARNINGS+%2B=+-Wall

TEMPLATE+=+lib

#+The+following+keeps+the+generated+files+at+least+somewhat+separate+
#+from+the+source+files.
UI_DIR+=+uics
MOC_DIR+=+mocs
OBJECTS_DIR+=+objs|1826382|logic/logic.pro：|1826383|#+Check+if+the+config+file+exists
!+include(+../common.pri+)+{
++++error(+"Couldn't+find+the+common.pri+file!"+)
}

HEADERS+%2B=+logic.h
SOURCES+%2B=+logic.cpp

#+By+default,+TARGET+is+the+same+as+the+directory,+so+it+will+make+
#+liblogic.a+(in+linux).++Uncomment+to+override.
#+TARGET+=+target|1826384|gui/gui.pro：|1826385|!+include(+../common.pri+)+{
++++error(+"Couldn't+find+the+common.pri+file!"+)
}

FORMS+%2B=+gui.ui
HEADERS+%2B=+gui.h
SOURCES+%2B=+gui.cpp

#+By+default,+TARGET+is+the+same+as+the+directory,+so+it+will+make+
#+libgui.a+(in+linux).++Uncomment+to+override.
#+TARGET+=+target|1826386|build/build.pro：|1826387|TEMPLATE+=+app

SOURCES+%2B=+main.cpp

LIBS+%2B=+-L../logic+-L../gui+-llogic+-lgui

#+Will+build+the+final+executable+in+the+main+project+directory.
TARGET+=+../project|1826388|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1417776/how-to-use-qmakes-subdirs-template/1417801#1417801^0|V|7|2|K|0|0|0|0|5|7|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|F|3|G|5|H|7|1O|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1P|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|1T|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|1U|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1V|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1W|8|@]|D|@]|E|$]]|$1|W|3|X|5|H|7|1X|8|@]|D|@]|E|$I|J]]|$1|Y|3|Z|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|10|3|11|5|H|7|1Z|8|@]|D|@]|E|$I|J]]|$1|12|3|13|5|6|7|20|8|@]|D|@]|E|$]]|$1|14|3|15|5|H|7|21|8|@]|D|@]|E|$I|J]]|$1|16|3|17|5|6|7|22|8|@]|D|@]|E|$]]|$1|18|3|19|5|H|7|23|8|@]|D|@]|E|$I|J]]|$1|1A|3|-4|5|6|7|24|8|@]|D|@]|E|$]]]|1B|$1C|$5|1D|1E|1F|E|$1G|1H]]]]

In addition to <a href="https://stackoverflow.com/questions/1417776/how-to-use-qmakes-subdirs-template/1417801#1417801">Troubadour's comment</a>, I would note that the <code>SUBDIRS</code> target is only good for specifying subdirectories. Therefore, your extra line of 

<pre><code>SOURCES += main.cpp
</code></pre>

in your project.pro file is incorrect, and will likely fail to build your main.cpp file, at worst. At best, qmake will refuse to parse the file, since it has conflicting specifications in it.

I've used the <code>SUBDIRS</code> template a few times, and it does well if you can build parts into more-or-less independent libraries, apparently like you have with the logic and the gui separate. Here is one way to do this:

<pre><code>project_dir/
-project.pro
-common.pri
-logic/
----logic.pro
----some logic files
-gui/
----gui.pro
----gui files
-build/
----build.pro
----main.cpp
</code></pre>

project.pro:

<pre><code>TEMPLATE = subdirs
SUBDIRS = logic \
 gui

# build must be last:
CONFIG += ordered
SUBDIRS += build
</code></pre>

common.pri:

<pre><code>#Includes common configuration for all subdirectory .pro files.
INCLUDEPATH += . ..
WARNINGS += -Wall

TEMPLATE = lib

# The following keeps the generated files at least somewhat separate 
# from the source files.
UI_DIR = uics
MOC_DIR = mocs
OBJECTS_DIR = objs
</code></pre>

logic/logic.pro:

<pre><code># Check if the config file exists
! include( ../common.pri ) {
 error( "Couldn't find the common.pri file!" )
}

HEADERS += logic.h
SOURCES += logic.cpp

# By default, TARGET is the same as the directory, so it will make 
# liblogic.a (in linux). Uncomment to override.
# TARGET = target
</code></pre>

gui/gui.pro:

<pre><code>! include( ../common.pri ) {
 error( "Couldn't find the common.pri file!" )
}

FORMS += gui.ui
HEADERS += gui.h
SOURCES += gui.cpp

# By default, TARGET is the same as the directory, so it will make 
# libgui.a (in linux). Uncomment to override.
# TARGET = target
</code></pre>

build/build.pro:

<pre><code>TEMPLATE = app

SOURCES += main.cpp

LIBS += -L../logic -L../gui -llogic -lgui

# Will build the final executable in the main project directory.
TARGET = ../project
</code></pre>

I'm starting to learn Qt. I'm moving from the Visual Studio world and I am looking for a way to organize my project's structure using QMake. I've found the 'subdirs' template but I have quite a hard time understanding it. 

My project structure looks like this: 

<pre><code>project_dir/
 main.cpp
 project.pro
 logic/
 logic.pro
 some logic files
 gui/
 gui.pro
 gui files
</code></pre>

My project.pro looks like this

<pre><code>TEMPLATE = subdirs
SUBDIRS = logic \
 gui
SOURCES += main.cpp
</code></pre>

In the .pro files for the subdirectories I have appropriate SOURCES, HEADERS and RESOURCES variables set.

Please tell me what TARGET, TEMPLATE and other necessary values I should set in the .pro files.

Also, is there some good QMake tutorial other than the official one?

How to use QMake's subdirs template?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我开始学习Qt了。我离开了Visual Studio世界，正在寻找一种使用QMake来组织我的项目结构的方法。我找到了“subdirs”模板，但我很难理解它。我的项目结构如下所示：project_dir/    main.cpp    project.pro    logic/      logic.pro      ...

问如何使用QMake的子目录模板？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用QMake的子目录模板？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用QMake的子目录模板？
EN