VS+QT和qtcreator工程的互相转换

墨蓝 2022-03-16 03:14 392阅读 0赞

QT Creator的project转成Visual Studio的project

在windows下，运行Qt Command Prompt。

输入命令行：

qmake -tp vc XXX.pro

会生成文件XXX.vcxproj

Visual Studio的project转成QT Creator的project

第一步，因为原Visual Studio工程就是基于QT Template的工程，所以我们可以用VS里的QT插件里的"Create basic .pro file..."菜单选项来自动生成一个.pro文件，实际上，不仅仅生成了.pro 文件，还生成了.pri文件。但是目前的.pro文件还是不能用的，因为其中还有大量的配置需要修改，比如INCLUDEPATH和LIBS.

第二步，修改.pro文件使其包含正确而必要的配置信息。  
总结笔者对.pro文件的具体修改如下：  
1. TEMPLATE = lib  
2. 将DESTDIR = xxx改成：  
Release:DESTDIR = xxx/Release  
Debug:DESTDIR = xxx/Debug  
3. CONFIG += debug\_and\_release  
4. 完善INCLUDEPATH  
5. 完善DEPENDPATH （这里又有故事了：事后笔者发现，只要在LIBS里写了-L"<LIBPATH>"，就没必要写DEPENDPATH了。）  
6. 加上 Release:DEPENDPATH 和 Debug:DEPENDPATH  
7. 类似的，完善LIBS，添加Release:LIBS和Debug:LIBS

第三步，双击改好的.pro文件，QT Creator打开此工程，选中合适的Kit，就可以build了。因为是64位机器，Kit选的是QT 5.5.1的msvc2013\_64.  
最后千万要注意的是，在系统环境变量%PATH%里，对于Visual Studio的编译器cl.exe和链接器link.exe, 要选对路径。比如，对于64位的机器，路径 C:\\Program Files (x86)\\Microsoft Visual Studio 12.0\\VC\\bin\\amd64 应该被加到%PATH%中，而不是 C:\\Program Files (x86)\\Microsoft Visual Studio 12.0\\VC\\bin 这一条在前一篇博文中已有详细阐述。

以上步骤做完后，就可以顺利地在QT Creator中进行build了。  
最后还要提醒的一点是，如果更改了.pro文件，想让更改生效，必须手动删除qmake生成的Makefile, Makefile.Debug和Makefile.Release文件。

下面是一个.pro文件的实例：  
\[plain\] view plain copy  
TEMPLATE = lib  
TARGET = MyProject  
Release:DESTDIR = ../../../Output/x64/Release  
Debug:DESTDIR = ../../../Output/x64/Debug  
QT += core qml  
CONFIG += debug\_and\_release  
DEFINES += WIN64 QT\_DLL QT\_QML\_LIB MyProject\_LIB  
  
INCLUDEPATH += ./GeneratedFiles \\  
. \\  
./GeneratedFiles/Release \\  
$$(VC\_INCLUDE) \\  
$$(VC\_INCLUDE)/../atlmfc/include \\  
$$(WINSDK\_INCLUDE)/shared \\  
$$(WINSDK\_INCLUDE)/um  
  
DEPENDPATH += . \\  
$$(WINSDK\_LIB)/um/x64 \\  
$$(VC\_LIB)/amd64 \\  
$$(QTDIR)/lib \\  
$$(QTDIR)/bin \\  
  
Release:DEPENDPATH += ../../../3rd\_library/opencv/libs/Release/x64 \\  
../../../3rd\_library/DirectShow/baseclasses/x64/Release  
  
Debug:DEPENDPATH += ../../../3rd\_library/opencv/libs/Debug/x64 \\  
../../../3rd\_library/DirectShow/baseclasses/x64/Debug  
  
MOC\_DIR += ./GeneratedFiles/release  
OBJECTS\_DIR += release  
UI\_DIR += ./GeneratedFiles  
RCC\_DIR += ./GeneratedFiles  
  
Release:LIBS += -L"../../../3rd\_library/DirectShow/baseclasses/x64/Release" \\  
\-lstrmbase \\  
\-L"../../../3rd\_library/opencv/libs/Release/x64" \\  
\-lqtmain \\  
\-lQt5Qml \\  
\-lQt5Core \\  
\-lopencv\_calib3d248 \\  
\-lopencv\_contrib248 \\  
\-lopencv\_core248 \\  
\-lopencv\_features2d248 \\  
\-lopencv\_flann248 \\  
\-lopencv\_gpu248 \\  
\-lopencv\_highgui248 \\  
\-lopencv\_imgproc248 \\  
\-lopencv\_legacy248 \\  
\-lopencv\_ml248 \\  
\-lopencv\_nonfree248 \\  
\-lopencv\_objdetect248 \\  
\-lopencv\_ocl248 \\  
\-lopencv\_photo248 \\  
\-lopencv\_stitching248 \\  
\-lopencv\_superres248 \\  
\-lopencv\_ts248 \\  
\-lopencv\_video248 \\  
\-lopencv\_videostab248  
  
Debug:LIBS += -L"../../../3rd\_library/DirectShow/baseclasses/x64/Debug" \\  
\-lstrmbasd \\  
\-L"../../../3rd\_library/opencv/libs/Debug/x64" \\  
\-lqtmaind \\  
\-lQt5Qmld \\  
\-lQt5Cored \\  
\-lopencv\_calib3d248d \\  
\-lopencv\_contrib248d \\  
\-lopencv\_core248d \\  
\-lopencv\_features2d248d \\  
\-lopencv\_flann248d \\  
\-lopencv\_gpu248d \\  
\-lopencv\_highgui248d \\  
\-lopencv\_imgproc248d \\  
\-lopencv\_legacy248d \\  
\-lopencv\_ml248d \\  
\-lopencv\_nonfree248d \\  
\-lopencv\_objdetect248d \\  
\-lopencv\_ocl248d \\  
\-lopencv\_photo248d \\  
\-lopencv\_stitching248d \\  
\-lopencv\_superres248d \\  
\-lopencv\_ts248d \\  
\-lopencv\_video248d \\  
\-lopencv\_videostab248d  
  
LIBS += -L"$$(WINSDK\_LIB)/um/x64" \\  
\-L"$$(VC\_LIB)/amd64" \\  
\-L"$$(QTDIR)/lib" \\  
\-L"$$(QTDIR)/bin" \\  
\-lWtsapi32 \\  
\-lPathcch \\  
\-l3DScanningEngine \\  
\-lUserenv \\  
\-lwinmm \\  
\-lMf \\  
\-lMfplat  
  
include(MyProject.pri)  
\---------------------  
转载原文：https://blog.csdn.net/lxj434368832/article/details/79558121