blocks|key|1070636|text|对于我的Qt项目，我在*.pro文件中使用了这个方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070637|HEADERS+%2B=+src/dialogs.h
SOURCES+%2B=+src/main.cpp+\
+++++++++++src/dialogs.cpp

Release:DESTDIR+=+release
Release:OBJECTS_DIR+=+release/.obj
Release:MOC_DIR+=+release/.moc
Release:RCC_DIR+=+release/.rcc
Release:UI_DIR+=+release/.ui

Debug:DESTDIR+=+debug
Debug:OBJECTS_DIR+=+debug/.obj
Debug:MOC_DIR+=+debug/.moc
Debug:RCC_DIR+=+debug/.rcc
Debug:UI_DIR+=+debug/.ui|code-block|syntax|javascript|1070638|这很简单，但是很好！:)|1070639|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For my Qt project, I use this scheme in *.pro file:

<pre><code>HEADERS += src/dialogs.h
SOURCES += src/main.cpp \
 src/dialogs.cpp

Release:DESTDIR = release
Release:OBJECTS_DIR = release/.obj
Release:MOC_DIR = release/.moc
Release:RCC_DIR = release/.rcc
Release:UI_DIR = release/.ui

Debug:DESTDIR = debug
Debug:OBJECTS_DIR = debug/.obj
Debug:MOC_DIR = debug/.moc
Debug:RCC_DIR = debug/.rcc
Debug:UI_DIR = debug/.ui
</code></pre>

It`s simple, but nice! :)

blocks|key|1285212|text|要更改目标dll/exe的目录，请在pro文件中使用以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285213|CONFIG(debug,+debug%7Crelease)+{
++++DESTDIR+=+build/debug
}+else+{
++++DESTDIR+=+build/release
}|code-block|syntax|javascript|1285214|您可能还希望更改其他构建目标的目录，如对象文件和moc文件(有关详细信息，请查看qmake+variable+reference或qmake+CONFIG()+function+reference)。|offset|length|1285215|entityMap|0|LINK|mutability|MUTABLE|url|http://qt-project.org/doc/qt-5/qmake-variable-reference.html|1|http://doc.qt.io/qt-4.8/qmake-function-reference.html#config-config^0|0|0|14|O|0|1T|X|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]|$I|10|J|11|1|12]]|A|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]]]

To change the directory for target dll/exe, use this in your pro file:

<pre><code>CONFIG(debug, debug|release) {
 DESTDIR = build/debug
} else {
 DESTDIR = build/release
}
</code></pre>

You might also want to change directories for other build targets like object files and moc files (check <a href="http://qt-project.org/doc/qt-5/qmake-variable-reference.html" rel="noreferrer">qmake variable reference</a> for details or <a href="http://doc.qt.io/qt-4.8/qmake-function-reference.html#config-config" rel="noreferrer">qmake CONFIG() function reference</a>).

blocks|key|1070688|text|我有一个更紧凑的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070689|release:+DESTDIR+=+build/release
debug:+++DESTDIR+=+build/debug

OBJECTS_DIR+=+$$DESTDIR/.obj
MOC_DIR+=+$$DESTDIR/.moc
RCC_DIR+=+$$DESTDIR/.qrc
UI_DIR+=+$$DESTDIR/.ui|code-block|syntax|javascript|1070690|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I have a more compact approach:

<pre><code>release: DESTDIR = build/release
debug: DESTDIR = build/debug

OBJECTS_DIR = $$DESTDIR/.obj
MOC_DIR = $$DESTDIR/.moc
RCC_DIR = $$DESTDIR/.qrc
UI_DIR = $$DESTDIR/.ui
</code></pre>

blocks|key|1070863|text|正确的方法如下(感谢QT支持团队)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1070864|CONFIG(debug,+debug%7Crelease)+{
++++DESTDIR+=+build/debug
}
CONFIG(release,+debug%7Crelease)+{
++++DESTDIR+=+build/release
}

OBJECTS_DIR+=+$$DESTDIR/.obj
MOC_DIR+=+$$DESTDIR/.moc
RCC_DIR+=+$$DESTDIR/.qrc
UI_DIR+=+$$DESTDIR/.u|code-block|syntax|javascript|1070865|更多信息请点击此处：https://wiki.qt.io/Qt_project_org_faq#What_does_the_syntax_CONFIG.28debug.2Cdebug.7Crelease.29_mean_.3F_What_does_the_1st_argument_specify_and_similarly_what_is_the_2nd_.3F|offset|length|1070866|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.qt.io/Qt_project_org_faq#What_does_the_syntax_CONFIG.28debug.2Cdebug.7Crelease.29_mean_.3F_What_does_the_1st_argument_specify_and_similarly_what_is_the_2nd_.3F^0|0|0|A|4S|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

The correct way to do this is the following (thanks QT Support Team):

<pre><code>CONFIG(debug, debug|release) {
 DESTDIR = build/debug
}
CONFIG(release, debug|release) {
 DESTDIR = build/release
}

OBJECTS_DIR = $$DESTDIR/.obj
MOC_DIR = $$DESTDIR/.moc
RCC_DIR = $$DESTDIR/.qrc
UI_DIR = $$DESTDIR/.u
</code></pre>

More info here: <a href="https://wiki.qt.io/Qt_project_org_faq#What_does_the_syntax_CONFIG.28debug.2Cdebug.7Crelease.29_mean_.3F_What_does_the_1st_argument_specify_and_similarly_what_is_the_2nd_.3F" rel="noreferrer">https://wiki.qt.io/Qt_project_org_faq#What_does_the_syntax_CONFIG.28debug.2Cdebug.7Crelease.29_mean_.3F_What_does_the_1st_argument_specify_and_similarly_what_is_the_2nd_.3F</a>

blocks|key|1285302|text|我使用chalup建议的相同方法，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285303|ParentDirectory+=+<your+directory>

RCC_DIR+=+"$$ParentDirectory\Build\RCCFiles"
UI_DIR+=+"$$ParentDirectory\Build\UICFiles"
MOC_DIR+=+"$$ParentDirectory\Build\MOCFiles"
OBJECTS_DIR+=+"$$ParentDirectory\Build\ObjFiles"

CONFIG(debug,+debug%7Crelease)+{+
++++DESTDIR+=+"$$ParentDirectory\debug"
}
CONFIG(release,+debug%7Crelease)+{+
++++DESTDIR+=+"$$ParentDirectory\release"
}|code-block|syntax|javascript|1285304|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I use the same method suggested by chalup,

<pre><code>ParentDirectory = &lt;your directory&gt;

RCC_DIR = "$$ParentDirectory\Build\RCCFiles"
UI_DIR = "$$ParentDirectory\Build\UICFiles"
MOC_DIR = "$$ParentDirectory\Build\MOCFiles"
OBJECTS_DIR = "$$ParentDirectory\Build\ObjFiles"

CONFIG(debug, debug|release) { 
 DESTDIR = "$$ParentDirectory\debug"
}
CONFIG(release, debug|release) { 
 DESTDIR = "$$ParentDirectory\release"
}
</code></pre>

blocks|key|1285490|text|老问题，但仍然值得一个最新的答案。今天，当使用影子构建时，Qt+Creator所做的事情是很常见的(当打开一个新项目时，它们是默认启用的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285491|对于每个不同的构建目标和类型，在不同的构建目录中使用正确的参数运行正确的qmake。然后，这就是用简单的make构建的。|offset|length|style|CODE|1285492|因此，假想的目录结构可能如下所示。|1285493|/
%7C_/build-mylib-qt5-mingw32-debug
%7C_/build-mylib-qt5-mingw32-release
%7C_/build-mylib-qt4-msvc2010-debug
%7C_/build-mylib-qt4-msvc2010-release
%7C_/build-mylib-qt5-arm-debug
%7C_/build-mylib-qt5-arm-release
%7C_/mylib
++%7C_/include
++%7C_/src
++%7C_/resources|code-block|syntax|javascript|1285494|重要的是，在构建目录中运行了一个qmake：|1285495|cd+build-mylib-XXXX
/path/to/right/qmake+../mylib/mylib.pro+CONFIG%2B=buildtype+...|1285496|然后它在build目录中生成makefile，然后make也会在该目录下生成文件。只要qmake从未在源目录中运行过(如果是，最好把它清理干净！)，就不会有不同版本混淆的风险。|1285497|当这样做时，来自当前接受的答案的.pro文件甚至更简单：|1285498|HEADERS+%2B=+src/dialogs.h
SOURCES+%2B=+src/main.cpp+\
+++++++++++src/dialogs.cpp|1285499|entityMap^0|0|10|5|1G|4|0|0|0|G|5|0|0|P|4|0|G|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|W|3|X|5|L|7|1I|8|@]|9|@]|A|$M|N]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$]]

Old question, but still worth an up-to-date answer. Today it's common to do what Qt Creator does when shadow builds are used (they are enabled by default when opening a new project).

For each different build target and type, the right <code>qmake</code> is run with right arguments in a different build directory. Then that is just built with simple <code>make</code>.

So, imaginary directory structure might look like this.

<pre><code>/
|_/build-mylib-qt5-mingw32-debug
|_/build-mylib-qt5-mingw32-release
|_/build-mylib-qt4-msvc2010-debug
|_/build-mylib-qt4-msvc2010-release
|_/build-mylib-qt5-arm-debug
|_/build-mylib-qt5-arm-release
|_/mylib
 |_/include
 |_/src
 |_/resources
</code></pre>

And the improtant thing is, a <code>qmake</code> is run in the build directory:

<pre><code>cd build-mylib-XXXX
/path/to/right/qmake ../mylib/mylib.pro CONFIG+=buildtype ...
</code></pre>

Then it generates makefiles in build directory, and then <code>make</code> will generate files under it too. There is no risk of different versions getting mixed up, as long as qmake is never run in the source directory (if it is, better clean it up well!).

And when done like this, the <code>.pro</code> file from currently accepted answer is even simpler:

<pre><code>HEADERS += src/dialogs.h
SOURCES += src/main.cpp \
 src/dialogs.cpp
</code></pre>

blocks|key|1285438|text|输出可执行文件的名称稍有不同也很有用。你不能使用像这样的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285439|release:+Target+=+ProgramName
debug:+Target+=+ProgramName_d|code-block|syntax|javascript|1285440|为什么它不起作用还不清楚，但它确实不起作用。但是：|1285441|CONFIG(debug,+debug%7Crelease)+{
++++TARGET+=+ProgramName
}+else+{
++++TARGET+=+ProgramName_d
}|1285442|只要CONFIG+%2B=行在它之前，它就可以工作。|offset|length|style|CODE|1285443|entityMap^0|0|0|0|0|2|9|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

It's also useful to have a slightly different name for the output executable. You can't use something like:

<pre><code>release: Target = ProgramName
debug: Target = ProgramName_d
</code></pre>

Why it doesn't work is not clear, but it does not. But: 

<pre><code>CONFIG(debug, debug|release) {
 TARGET = ProgramName
} else {
 TARGET = ProgramName_d
}
</code></pre>

This does work as long as the <code>CONFIG +=</code> line precedes it.

blocks|key|1285589|text|新版本的Qt+Creator也有一个在调试和发布之间的“配置文件”构建选项。下面是我是如何检测到的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285590|CONFIG(debug,+debug%7Crelease)+{++DEFINES+%2B=+DEBUG_MODE+}
else:CONFIG(force_debug_info)+{+DEFINES+%2B=+PROFILE_MODE+}
else+{++++++++++++++++++++++++++DEFINES+%2B=+RELEASE_MODE+}|code-block|syntax|javascript|1285591|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The new version of Qt Creator also has a "profile" build option between debug and release. Here's how I'm detecting that:

<pre><code>CONFIG(debug, debug|release) { DEFINES += DEBUG_MODE }
else:CONFIG(force_debug_info) { DEFINES += PROFILE_MODE }
else { DEFINES += RELEASE_MODE }
</code></pre>

blocks|key|1285619|text|这是我的Makefile，用于不同的调试/发布输出目录。这个Makefile在Ubuntu+linux上测试成功。如果正确安装了Mingw-w64，它应该可以在Windows上无缝工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285620|ifeq+($(OS),Windows_NT)
++++ObjExt=obj
++++mkdir_CMD=mkdir
++++rm_CMD=rmdir+/S+/Q
else
++++ObjExt=o
++++mkdir_CMD=mkdir+-p
++++rm_CMD=rm+-rf
endif

CC+++++=gcc
CFLAGS+=-Wall+-ansi
LD+++++=gcc

OutRootDir=.
DebugDir++=Debug
ReleaseDir=Release


INSTDIR+=./bin
INCLUDE+=.

SrcFiles=$(wildcard+*.c)
EXEC_main=myapp

OBJ_C_Debug+++=$(patsubst+%25.c,++$(OutRootDir)/$(DebugDir)/%25.$(ObjExt),$(SrcFiles))
OBJ_C_Release+=$(patsubst+%25.c,++$(OutRootDir)/$(ReleaseDir)/%25.$(ObjExt),$(SrcFiles))

.PHONY:+Release+Debug+cleanDebug+cleanRelease+clean

#+Target+specific+variables
release:+CFLAGS+%2B=+-O+-DNDEBUG
debug:+++CFLAGS+%2B=+-g

################################################
#Callable+Targets
release:+$(OutRootDir)/$(ReleaseDir)/$(EXEC_main)
debug:+++$(OutRootDir)/$(DebugDir)/$(EXEC_main)

cleanDebug:
++++-$(rm_CMD)+"$(OutRootDir)/$(DebugDir)"
++++@echo+cleanDebug+done

cleanRelease:
++++-$(rm_CMD)+"$(OutRootDir)/$(ReleaseDir)"
++++@echo+cleanRelease+done

clean:+cleanDebug+cleanRelease
################################################

#+Pattern+Rules
#+Multiple+targets+cannot+be+used+with+pattern+rules+[https://www.gnu.org/software/make/manual/html_node/Multiple-Targets.html]
$(OutRootDir)/$(ReleaseDir)/%25.$(ObjExt):+%25.c+%7C+$(OutRootDir)/$(ReleaseDir)
++++$(CC)+-I$(INCLUDE)+$(CFLAGS)+-c+$<+-o"$@"

$(OutRootDir)/$(DebugDir)/%25.$(ObjExt):+++%25.c+%7C+$(OutRootDir)/$(DebugDir)
++++$(CC)+-I$(INCLUDE)+$(CFLAGS)+-c+$<+-o"$@"

#+Create+output+directory
$(OutRootDir)/$(ReleaseDir)+$(OutRootDir)/$(DebugDir)+$(INSTDIR):
++++-$(mkdir_CMD)+$@

#+Create+the+executable
#+Multiple+targets+[https://www.gnu.org/software/make/manual/html_node/Multiple-Targets.html]
$(OutRootDir)/$(ReleaseDir)/$(EXEC_main):+$(OBJ_C_Release)
$(OutRootDir)/$(DebugDir)/$(EXEC_main):+++$(OBJ_C_Debug)
$(OutRootDir)/$(ReleaseDir)/$(EXEC_main)+$(OutRootDir)/$(DebugDir)/$(EXEC_main):
++++$(LD)+$%5E+-o$@|code-block|syntax|javascript|1285621|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is my Makefile for different debug/release output directories. This Makefile was tested successfully on Ubuntu linux. It should work seamlessly on Windows provided that Mingw-w64 is installed correctly.

<pre><code>ifeq ($(OS),Windows_NT)
 ObjExt=obj
 mkdir_CMD=mkdir
 rm_CMD=rmdir /S /Q
else
 ObjExt=o
 mkdir_CMD=mkdir -p
 rm_CMD=rm -rf
endif

CC =gcc
CFLAGS =-Wall -ansi
LD =gcc

OutRootDir=.
DebugDir =Debug
ReleaseDir=Release


INSTDIR =./bin
INCLUDE =.

SrcFiles=$(wildcard *.c)
EXEC_main=myapp

OBJ_C_Debug =$(patsubst %.c, $(OutRootDir)/$(DebugDir)/%.$(ObjExt),$(SrcFiles))
OBJ_C_Release =$(patsubst %.c, $(OutRootDir)/$(ReleaseDir)/%.$(ObjExt),$(SrcFiles))

.PHONY: Release Debug cleanDebug cleanRelease clean

# Target specific variables
release: CFLAGS += -O -DNDEBUG
debug: CFLAGS += -g

################################################
#Callable Targets
release: $(OutRootDir)/$(ReleaseDir)/$(EXEC_main)
debug: $(OutRootDir)/$(DebugDir)/$(EXEC_main)

cleanDebug:
 -$(rm_CMD) "$(OutRootDir)/$(DebugDir)"
 @echo cleanDebug done

cleanRelease:
 -$(rm_CMD) "$(OutRootDir)/$(ReleaseDir)"
 @echo cleanRelease done

clean: cleanDebug cleanRelease
################################################

# Pattern Rules
# Multiple targets cannot be used with pattern rules [https://www.gnu.org/software/make/manual/html_node/Multiple-Targets.html]
$(OutRootDir)/$(ReleaseDir)/%.$(ObjExt): %.c | $(OutRootDir)/$(ReleaseDir)
 $(CC) -I$(INCLUDE) $(CFLAGS) -c $&lt; -o"$@"

$(OutRootDir)/$(DebugDir)/%.$(ObjExt): %.c | $(OutRootDir)/$(DebugDir)
 $(CC) -I$(INCLUDE) $(CFLAGS) -c $&lt; -o"$@"

# Create output directory
$(OutRootDir)/$(ReleaseDir) $(OutRootDir)/$(DebugDir) $(INSTDIR):
 -$(mkdir_CMD) $@

# Create the executable
# Multiple targets [https://www.gnu.org/software/make/manual/html_node/Multiple-Targets.html]
$(OutRootDir)/$(ReleaseDir)/$(EXEC_main): $(OBJ_C_Release)
$(OutRootDir)/$(DebugDir)/$(EXEC_main): $(OBJ_C_Debug)
$(OutRootDir)/$(ReleaseDir)/$(EXEC_main) $(OutRootDir)/$(DebugDir)/$(EXEC_main):
 $(LD) $^ -o$@
</code></pre>

blocks|key|1071021|text|不确定是否有人会面临像我一样的问题，但我会分享我的设置。我使用一个中央proj.pri文件来存储常规设置。我在每个子目录中都有PKG.pro，它已经是为调试模式设计的。因此，当我尝试构建调试和发布时，我不想修改每个子目录中的每个PKG.pro。我添加了相同的内容|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1071022|DESTDIR+=+$${SOMEOTHERPATH}
release:+DESTDIR+=+$${DESTDIR}/release
debug:+++DESTDIR+=+$${DESTDIR}/debug

OBJECTS_DIR+=+$$DESTDIR/.obj
MOC_DIR+=+$$DESTDIR/.moc
RCC_DIR+=+$$DESTDIR/.qrc
UI_DIR+=+$$DESTDIR/.ui|code-block|syntax|javascript|1071023|这不起作用，因为在每个子目录中，DESTDIR都会再次求值。它将结束双重调试或释放。为了避免这种情况，您必须只使用一个DESTDIR集，然后在每个子目录中，您可以包含此proj.pri文件。这样，您不需要编写一个DIR设置。构建调试或发布时需要qmake+CONFIG=debug或qmake+CONFIG=release。任何人有更好的解决方案，请分享。|1071024|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Not sure if anyone will face issues like me, but I'd share my setup.
I use a central proj.pri file to store general settings. I have PKG.pro in each subdirs which is already designed for debug mode. So when I try to build both debug and release, I don't want to modify every PKG.pro in each subdir. I added same
<pre><code>DESTDIR = $${SOMEOTHERPATH}
release: DESTDIR = $${DESTDIR}/release
debug: DESTDIR = $${DESTDIR}/debug

OBJECTS_DIR = $$DESTDIR/.obj
MOC_DIR = $$DESTDIR/.moc
RCC_DIR = $$DESTDIR/.qrc
UI_DIR = $$DESTDIR/.ui
</code></pre>
which doesn't work since in each subdir, DESTDIR will get evaluated again. it ends a double debug or release. To avoid this, you have to use only one DESTDIR set, then in each subdir, you can include this proj.pri file. This way, you don't need to write one DIR setup.
And &quot;qmake CONFIG=debug&quot; or &quot;qmake CONFIG=release&quot; is needed to build debug or release.
Anyone has better solution, please share.

I have a Qt project and I would like to output compilation files outside the source tree.

I currently have the following directory structure:

<pre><code>/
|_/build
|_/mylib
 |_/include
 |_/src
 |_/resources
</code></pre>

Depending on the configuration (debug/release), I will like to output the resulting files inside the build directory under build/debug or build/release directories.

How can I do that using a .pro file?

How to specify different Debug/Release output directories in QMake .pro file

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

问如何在QMake .pro文件中指定不同的调试/发布输出目录
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在QMake .pro文件中指定不同的调试/发布输出目录EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在QMake .pro文件中指定不同的调试/发布输出目录
EN