qmake 中 debug_and_release 配置功能的优点是什么? [英] What are the merits of debug_and_release config feature in qmake?

查看:67
本文介绍了qmake 中 debug_and_release 配置功能的优点是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我只能看到该功能的一个优点:我们可以发出 make all 命令.

好吧,我在开发人员的任何时候都不会调用 make.我使用 Qt Creator,当我构建项目时,我希望它严格作为调试或发布.我想这是人们的一种预期行为.

但是 debug_and_release 在 Qt Creator 中默认是开启的.这有什么我看不到的优点吗?像这样不直观的混乱是否有某种意义:

<前>配置(调试,调试|发布){# 调试} 别的 {# 释放}

哪些人是通过在互联网上犯错和问 WTF 问题来学习的?

我错过了什么吗?

解决方案

我把它关了:

<前>配置 -= debug_and_release配置(调试,调试|发布){配置 -= 发布}别的 {配置 -= 调试配置 += 发布}

更新.

我知道了.我的问题是完全错误的.debug_and_releasedebugrelease 没有太大关系.

I can see only one merit of the feauture: we are able to issue the make all commad.

Well, I do not call make in any point of my developer's life. I use Qt Creator and when I build the project I want it strictly as debug or as release. I guess this is an expeted behaviour by people.

But debug_and_release is on by default in Qt Creator. Is there a merit in this I can't see? Is there some sense in the unintuitive mess like this:

CONFIG( debug, debug|release ) {
    # debug
} else {
    # release
}

which people are learning by making mistakes and asking WTF questions all over the internet?

Am I missing something?

解决方案

I switch it off:

CONFIG -= debug_and_release
CONFIG( debug, debug|release )  {
  CONFIG -= release
}
else {
  CONFIG -= debug
  CONFIG += release
}

UPD.

I've got it. My question is completely wrong. debug_and_release have not much to do with debug and release.

这篇关于qmake 中 debug_and_release 配置功能的优点是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆