Configuring Qt-Embedded with directFB
Hello all,
I'm having a problem with DirecFB plugin.
I've downloaded the newest version of Qt-embedded (4.5.2) and tried out the following :
"./configure -opensource -static -exceptions -no-qt3support -no-phonon -no-phonon-backend -qt-zlib -qt-libtiff -qt-libpng -qt-libmng -qt-libjpeg -silent -xplatform qws/linux-i386-g++ -embedded x86 -little-endian -host-little-endian -qt-freetype -depths all -qt-gfx-linuxfb -plugin-gfx-directfb -qt-kbd-tty -qt-mouse-tslib -prefix /usr/local/Trolltech/QtEmbedded-4.5.2-directfb"
And the configure stops, reporting this:
"The DirectFB screen driver functionality test failed!
You might need to modify the include and library search paths by editing
QT_CFLAGS_DIRECTFB and QT_LIBS_DIRECTFB in
/home/eduardo/temp/qt-embedded-linux-opensource-src-4.5.2/mkspecs/qws/linux-i386-g++."
I have the DirectFB installed on my machine, and the dev packages also (libdirectfb-1.0-0 and libdirectfb-dev).
So, I 've edited the qmake.conf in /home/eduardo/temp/qt-embedded-linux-opensource-src-4.5.2/mkspecs/qws/linux-i386-g++ and add :
QT_CFLAGS_DIRECTFB=-I/usr/include/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L/usr/lib -ldirectfb -lfusion -ldirect -lpthread
But that didn't work.
I donn't know what else I can do.
Any help will be welcome.
Regards,
Re: Configuring Qt-Embedded with directFB
Since I was cross-compiling, I've created a "/mkspecs/qws/linux-i386-g++/QMake.conf" for my target architecture and I should had pointed the DirectFB flags to my target libs, not to my host.
So, that fixed the problem :
QT_CFLAGS_DIRECTFB=-I/home/eduardo/toolchain/usr/include/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L/home/eduardo/toolchain/usr/lib -ldirectfb -lfusion -ldirect -lpthread
Re: Configuring Qt-Embedded with directFB
Hello
I have a similar problem, but the solution you provide doesn`t work for me. I am developing for a mips platform and I have directfb for the target device. In fact, I have some applications and examples running that use directfb.
The thing is that when I try to configure Qt (4.4.3) to use directfb in this way:
" ./configure -embedded mips -xplatform qws/linux-mips-g++ -qt-gfx-linuxfb -plugin-gfx-directfb"
I get this message:
"The DirectFB screen driver functionality test failed!
You might need to modify the include and library search paths by editing
QMAKE_INCDIR and QMAKE_LIBDIR in
/home/alex/PR15/qt-embedded-linux-opensource-src-4.4.3/mkspecs/qws/linux-mips-g++"
Then I edit the file /home/alex/PR15/qt-embedded-linux-opensource-src-4.4.3/mkspecs/qws/linux-mips-g++/qmake.conf to append these two statements at the end:
QT_CFLAGS_DIRECTFB=-I$(PRJROOT)/build_generic/staging/usr/include/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L$(PRJROOT)/build_generic/staging/usr/lib -ldirectfb -lfusion -ldirect -lpthread
after that I run the configuration and the message keeps the same.
Am I doing something wrong? Please, any help would be appreciated.
Bye.
Re: Configuring Qt-Embedded with directFB
Quote:
Originally Posted by
lar_fer
Hello
I have a similar problem, but the solution you provide doesn`t work for me. I am developing for a mips platform and I have directfb for the target device. In fact, I have some applications and examples running that use directfb.
The thing is that when I try to configure Qt (4.4.3) to use directfb in this way:
" ./configure -embedded mips -xplatform qws/linux-mips-g++ -qt-gfx-linuxfb -plugin-gfx-directfb"
I get this message:
"The DirectFB screen driver functionality test failed!
You might need to modify the include and library search paths by editing
QMAKE_INCDIR and QMAKE_LIBDIR in
/home/alex/PR15/qt-embedded-linux-opensource-src-4.4.3/mkspecs/qws/linux-mips-g++"
Then I edit the file /home/alex/PR15/qt-embedded-linux-opensource-src-4.4.3/mkspecs/qws/linux-mips-g++/qmake.conf to append these two statements at the end:
QT_CFLAGS_DIRECTFB=-I$(PRJROOT)/build_generic/staging/usr/include/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L$(PRJROOT)/build_generic/staging/usr/lib -ldirectfb -lfusion -ldirect -lpthread
after that I run the configuration and the message keeps the same.
Am I doing something wrong? Please, any help would be appreciated.
Bye.
i configure is:
Quote:
./configure -embedded mips -xplatform qws/linux-mips-g++ -little-endian -no-qvfb
but when make then it errror:
Quote:
root@admin-laptop:/home/sonnh/qt-everywhere-opensource-src-4.7.0# cd demos/books/
root@admin-laptop:/home/sonnh/qt-everywhere-opensource-src-4.7.0/demos/books# make
mips-linux-g++ -c -pipe -mips32 -fno-exceptions -O2 -Wall -W -D_REENTRANT -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I../../mkspecs/qws/linux-mips-g++ -I. -I../../include/QtCore -I../../include/QtNetwork -I../../include/QtGui -I../../include/QtSql -I../../include -I. -I.moc/release-shared-emb-mips -I.uic/release-shared-emb-mips -o .obj/release-shared-emb-mips/bookdelegate.o bookdelegate.cpp
make: mips-linux-g++: Command not found
make: *** [.obj/release-shared-emb-mips/bookdelegate.o] Error 127
Re: Configuring Qt-Embedded with directFB
Quote:
make: mips-linux-g++: Command not found
make: *** [.obj/release-shared-emb-mips/bookdelegate.o] Error 127
You have to search for your cross compiler directory. You might have something called mipsel-linux-g++ or similar instead of mips-linux-g++. You should link the actual g++ to the one that qt is asking you. For example:
you don't have mips-linux-g++ but you have mipsel-linux-g++ then, place where the croos compiler is and:
user@whereeveryouare$ln -s mipsel-linux-g++ mips-linux-g++
bye
Re: Configuring Qt-Embedded with directFB
I do have the same problem here. I try to configure with directFB. The directfb I want to use is provided by the vendor of the system I want to use, and it works well.
So here is the configure line I'm using :
./configure -embedded arm-gnueabi -qt-freetype -embedded arm-gnueabi -plugin-gfx-directfb -xplatform qws/linux-arm-gnueabi-g++
The compiler I what to use is in the PATH and I precise the name of the binary in qmake.conf.
Here is how I set QT_CFLAGS_DIRECTFB and QT_LIBS_DIRECTFB at the end of qws/linux-arm-gnueabi-g++/qmake.conf :
QT_CFLAGS_DIRECTFB=-I/opt/SDK/inc/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L/opt/SDK/lib -ldirectfb -lfusion -ldirect -lpthread
But I get this whatever I'm doing :
Do you accept the terms of either license? yes
Creating qmake. Please wait...
make: Rien à faire pour « first ».
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
(many like theses)
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
The DirectFB screen driver functionality test failed!
You might need to modify the include and library search paths by editing
QT_CFLAGS_DIRECTFB and QT_LIBS_DIRECTFB in
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/mkspecs/qws/linux-arm-gnueabi-g++.
Do I miss something ?
Re: Configuring Qt-Embedded with directFB
Quote:
Originally Posted by
lar_fer
You have to search for your cross compiler directory. You might have something called mipsel-linux-g++ or similar instead of mips-linux-g++. You should link the actual g++ to the one that qt is asking you. For example:
you don't have mips-linux-g++ but you have mipsel-linux-g++ then, place where the croos compiler is and:
user@whereeveryouare$ln -s mipsel-linux-g++ mips-linux-g++
bye
Either provide the cross-compiler tool chain path for mips-linux-g++ in qmake.conf or export the cross-compiler toolchain path to path.
Ex: export PATH=$PATH:path/to/crosscompiler/toolchain
Re: Configuring Qt-Embedded with directFB
Quote:
Originally Posted by
Agrou
I do have the same problem here. I try to configure with directFB. The directfb I want to use is provided by the vendor of the system I want to use, and it works well.
So here is the configure line I'm using :
./configure -embedded arm-gnueabi -qt-freetype -embedded arm-gnueabi -plugin-gfx-directfb -xplatform qws/linux-arm-gnueabi-g++
The compiler I what to use is in the PATH and I precise the name of the binary in qmake.conf.
Here is how I set QT_CFLAGS_DIRECTFB and QT_LIBS_DIRECTFB at the end of qws/linux-arm-gnueabi-g++/qmake.conf :
QT_CFLAGS_DIRECTFB=-I/opt/SDK/inc/directfb -D_REENTRANT
QT_LIBS_DIRECTFB=-L/opt/SDK/lib -ldirectfb -lfusion -ldirect -lpthread
But I get this whatever I'm doing :
Do you accept the terms of either license? yes
Creating qmake. Please wait...
make: Rien à faire pour « first ».
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
(many like theses)
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/bin/qmake: 1: Syntax error: word unexpected (expecting ")")
The DirectFB screen driver functionality test failed!
You might need to modify the include and library search paths by editing
QT_CFLAGS_DIRECTFB and QT_LIBS_DIRECTFB in
/home/devel-arm/libs/qt-everywhere-opensource-src-4.7.1/mkspecs/qws/linux-arm-gnueabi-g++.
Do I miss something ?
you must rebuild DirectFB by Cross Compile arm, you cant use package libdirectfb-1.0-0 and libdirectfb-dev on Ubuntu
Re: Configuring Qt-Embedded with directFB
hi all, the first, you must test by cd /tango3/qt_SMP8654F_bin_4.5.2-1.1/src/config.tests/qws/directfb and make file it, its is test of QT, if you test success, then you will builded, i was test, all thing good
Re: Configuring Qt-Embedded with directFB
Ex: Error:
Quote:
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmpacketcommand.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmdisc.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmdvdfs.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmdvdfsapi.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmdvdvideonav.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmdvdvideoapi.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmcdda.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
/home/sonnh/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/mips-linux-gnu/4.3.2/../../../../mips-linux-gnu/bin/ld: warning: librmcddanavapi.so, needed by /tango3/dcchd_SMP8652_3_8_2_aqua.mips/dcchd/dcchd/libdcchd.so, not found (try using -rpath or -rpath-link)
make: *** [directfb] Error 1
