|
Thilloy Paul
05/23/2014 5:08 AM
post110468
|
Hi guys,
I tried to compile Qt 5.3 as it was just released...
But I stumbled into a compilation error :
../shared/qmakeglobals.cpp: In member function 'bool QMakeGlobals::initProperties()':
../shared/qmakeglobals.cpp:324:85: error: '_popen' was not declared in this scope
+ QLatin1String(" -query")).toLocal8Bit(), "r")) {
^
../shared/qmakeglobals.cpp:328:23: error: '_pclose' was not declared in this scope
QT_PCLOSE(proc);
^
It seems that there is a problem regarding the popen or pclose function...
I tried to dig a little bit ... but I have a question...cross compiling Qt for Qnx on a Windows machine... which stdio.h
is used ? The one from qnx660 or from MingW ?
Here is the process I follow to compile Qt : In a command window:
# c:\qnx660\qnx660-env.bat
# cd C:\QtQNX\qt-everywhere-opensource-src-5.3.0\
# configure -release -nomake examples -nomake tests -prefix C:\QtQNX\qt5-5.3 -platform win32-g++ -xplatform qnx-armle-
v7-qcc -opengl es2 -no-cups -no-iconv -skip qtserialport -skip qtwebkit -skip qtmultimedia -mp
(-skip multimedia because I didn't install the Qnx App and Media as I don't need it right now)
This configure line is the one from Qt5.2 ... in the Qnx wiki from Qt-project, the configure command is way shorter..is
it normal ?
then # make -j4
First I got a problem with
In file included from ../shared/translator.cpp:54:0:
c:\mingw\include\io.h:301:14: error: 'off64_t' does not name a type
__CRT_INLINE off64_t lseek64 (int, off64_t, int);
^
c:\mingw\include\io.h:302:14: error: 'off64_t' does not name a type
__CRT_INLINE off64_t lseek64 (int fd, off64_t offset, int whence) {
^
make[5]: *** [.obj/release/translator.o] Error 1
=> I just changed the c:\mingw\include\io.h : changed the occurences of 'off64_t' to '_off64_t' , that solved the
problem..
then again
# make -j4
=> the popen/pclose problem...(if I look at the qmakeglobals.cpp:
#ifdef Q_OS_WIN32
#define QT_POPEN _popen
#define QT_PCLOSE _pclose
#else
#define QT_POPEN popen
#define QT_PCLOSE pclose
#endif
=> Are we on Q_OS_WIN32 ???
Do you have any kind of way around this problem...or perhaps should I wait a few days (weeks ?) and get a perfectly
compiled QtQnx version from your "File Releases"
Regards,
Paul
|
|
|
|
|
