Qt5 在Linux 下的编译,该怎么处理

Qt5 在Linux 下的编译,该怎么处理,第1张

[wanglj@localhost testQT]$ make

g++ -o testQT main.o-L/opt/Qt5.1.1/5.1.1/gcc_64/lib -lqt-mt -lXext -lX11 -lm

main.o: In function `main':

/home/wanglj/testQT/main.cpp:6: undefined reference to `QApplication::QApplication(int&, char**, int)'

main.o: In function `QString':

/usr/include/QtCore/qstring.h:413: undefined reference to `QString::fromAscii_helper(char const*, int)'

main.o: In function `main':

/home/wanglj/testQT/main.cpp:7: undefined reference to `QLabel::QLabel(QString const&, QWidget*, QFlags<Qt::WindowType>)'

main.o: In function `~QString':

/usr/include/QtCore/qstring.h:869: undefined reference to `QString::free(QString::Data*)'

/usr/include/QtCore/qstring.h:869: undefined reference to `QString::free(QString::Data*)'

collect2: ld 返回 1

make: *** [testQT] 错误 1

但若直接用 qtcreator 打开编译,则无错误

并且find -name libqt-mt* 也找不到其他版本的该文件

用qtcreator编译好的可执行文件,也找不到连接该lib文件

[wanglj@localhost build-testQT-桌面-Debug]$ ldd testQT

linux-vdso.so.1 => (0x00007fff4ddff000)

libQtGui.so.4 =>/usr/lib64/libQtGui.so.4 (0x000000397f000000)

libQtCore.so.4 =>/usr/lib64/libQtCore.so.4 (0x000000397ea00000)

libpthread.so.0 =>/lib64/libpthread.so.0 (0x0000003978600000)

libstdc++.so.6 =>/usr/lib64/libstdc++.so.6 (0x00007fda6a081000)

libm.so.6 =>/lib64/libm.so.6 (0x0000003977a00000)

libgcc_s.so.1 =>/lib64/libgcc_s.so.1 (0x0000003983a00000)

libc.so.6 =>/lib64/libc.so.6 (0x0000003977e00000)

libgthread-2.0.so.0 =>/lib64/libgthread-2.0.so.0 (0x000000397a600000)

librt.so.1 =>/lib64/librt.so.1 (0x0000003978e00000)

libglib-2.0.so.0 =>/lib64/libglib-2.0.so.0 (0x0000003979200000)

libpng12.so.0 =>/usr/lib64/libpng12.so.0 (0x000000397be00000)

libz.so.1 =>/lib64/libz.so.1 (0x0000003978a00000)

libfreetype.so.6 =>/usr/lib64/libfreetype.so.6 (0x000000397ba00000)

libgobject-2.0.so.0 =>/lib64/libgobject-2.0.so.0 (0x0000003979e00000)

libSM.so.6 =>/usr/lib64/libSM.so.6 (0x0000003985a00000)

libICE.so.6 =>/usr/lib64/libICE.so.6 (0x0000003984e00000)

libXi.so.6 =>/usr/lib64/libXi.so.6 (0x000000397ce00000)

libXrender.so.1 =>/usr/lib64/libXrender.so.1 (0x000000397d600000)

libXrandr.so.2 =>/usr/lib64/libXrandr.so.2 (0x000000397de00000)

libXfixes.so.3 =>/usr/lib64/libXfixes.so.3 (0x000000397da00000)

libXcursor.so.1 =>/usr/lib64/libXcursor.so.1 (0x000000397e200000)

libXinerama.so.1 =>/usr/lib64/libXinerama.so.1 (0x000000397e600000)

libfontconfig.so.1 =>/usr/lib64/libfontconfig.so.1 (0x000000397d200000)

libXext.so.6 =>/usr/lib64/libXext.so.6 (0x000000397c600000)

libX11.so.6 =>/usr/lib64/libX11.so.6 (0x000000397b600000)

libdl.so.2 =>/lib64/libdl.so.2 (0x0000003978200000)

/lib64/ld-linux-x86-64.so.2 (0x0000003977600000)

libuuid.so.1 =>/lib64/libuuid.so.1 (0x0000003983600000)

libexpat.so.1 =>/lib64/libexpat.so.1 (0x000000397c200000)

libxcb.so.1 =>/usr/lib64/libxcb.so.1 (0x000000397ae00000)

libXau.so.6 =>/usr/lib64/libXau.so.6 (0x000000397aa00000)

------解决方案--------------------

INCPATH = -I/usr/lib64/qt-3.3/mkspecs/default -I. -I. -I$(QTDIR)/include

这一行看上去你调用的qmake不是5.1.1的。试试指定完整路径运行qmake

/opt/Qt5.1.1/5.1.1/gcc_64/bin/qmake testQT.pro

1,如果同时打开静态库和运行程序调用,调式模式下,可以进入静态库的内部函数进行调试;

2,其实不用把shadow build取消勾选;文件输出的文件就是lib***.a的文件,可以在shadow目录里面很方便找到;

3,新的项目使用的时候,就是让其能找到lib***.a,和该库的h头文件;

4,QT的编译输出的静态库名字会自动在项目名字前加lib三个字,后缀是.a;

5, QT5.15的编程的工程与该例子中缺少“需要什么模块就添加什么”的部分;


欢迎分享,转载请注明来源:内存溢出

原文地址: http://outofmemory.cn/yw/8931617.html

(0)
打赏 微信扫一扫 微信扫一扫 支付宝扫一扫 支付宝扫一扫
上一篇 2023-04-23
下一篇 2023-04-23

发表评论

登录后才能评论

评论列表(0条)

保存