| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On the Mac, it means "-framework ApplicationServices -framework Carbon
-framework AppKit" are no longer part of the default LIBS in Qt
applications. This required a lot of fixes where we used Mac-specific
code in Qt.
On X11, it was very straightforward, because we apparently use very
little of X11 outside QtGui.
I haven't changed the Windows-specific LIBS paths, because I don't
know how Windows behaves. Windows has DLLs, but it links to static
"import" libraries. So is it static linking or dynamic linking?
Reviewed-By: Marius Storm-Olsen
|
|
|
|
|
|
|
| |
Instead of hard coding "make", use "$MAKE". If $MAKE is not set,
configure will export it for us when searching for "make".
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason is that the C++ compiler needs to add -I/usr/vacpp/include
before -I/usr/include, so our adding of -I/usr/include changes the order.
This causes a compilation error in the C++ header xlocinfo.h.
In any case, these checks done in qmake are unnecessary. If the OpenSSL
headers are in one of those include paths, they will be found on their
own already.
Reviewed-By: Bradley T. Hughes
|
|
|
|
|
|
|
|
| |
This makes Qt work on QNX 6.4.
* no q3support, no phonon
* no QSharedMemory, no QSystemSemaphore, no QProcess
Reviewed-By: Robert Griebl
|
|
|
|
|
|
|
|
|
|
| |
At least the RogueWave STL found in Sun Studio 12 (latest version
available) isn't standards-compliant enough for QtConcurrent's needs.
Note that WebKit also requires STL support, so this means QtWebKit
will not compile with RW STL on Solaris.
Reviewed-By: Bradley T. Hughes
|
|
|
|
|
|
|
| |
It was reported to be auto-detected, but wasn't. Apparently, AIX 6's
X11 doesn't have this.
Reviewed-By: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/network/access/qnetworkreplyimpl.cpp
|
| |
| |
| |
| |
| |
| |
| | |
I don't know why, even though it's specified in POSIX. But we have to
cope with broken stuff.
Reviewed-by: Bradley T. Hughes
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qsqldatabase/tst_databases.h
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I have been bitten by this quite often and I had never found out why
suddenly configure decided to erase all my build. It happens that my
"make" replacement script command tries to search for a Makefile in
the parent dirs (so I can run "make" while inside src/corelib/tools),
and this caused the whole build to be erased.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| | |
ShivaVG runs on top of OpenGL. Include the QMAKE_*_OPENGL flags
on the link line if it is needed by the OpenVG engine.
Reviewed-by: trustme
|
| |
| |
| |
| |
| | |
This change also moves the EGL support classes from QtOpenGL to QtGui
so they can be shared between OpenGL and OpenVG.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This makes sure that we only detect and use libraries that are actually
in the SDK.
Task-number: 109757
Reviewed-by: Richard Moe Gustavsen
|
| |
| |
| |
| |
| |
| | |
If unixodbc detection fails, try and link/detect iodbc libraries and link against them.
Reviewed-by: Lincoln Ramsay
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
src/gui/kernel/qcocoaview_mac_p.h
src/gui/widgets/qmainwindow.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
architechtures.
For example,
./configure -arch x86_64 -arch ppc requires D-Bus compiled for x86_64 and ppc
in order to enable it.
Task-number: 249881
Reviewed-by: nrc
|
|/
|
|
|
|
|
| |
Quote a few variables that may contain spaces. Also, quote spaces
in qmake's Makefile dependency section.
Reviewed-by: Friedemann Kleint <qtc-committer@nokia.com>
|
|
|
|
|
|
|
|
|
| |
The OpenGL ES config tests are there to test if there's enough to build
QtOpenGL, not OpenGL applications using Qt. Therefore we should use
QMAKE_LIBS_OPENGL_QT rather than QMAKE_LIBS_OPENGL. This is mostely
because Qt needs to link against EGL whereas Qt applications do not.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
Previously, it was entirely possible to successfully configure Qt/X11
without any X11 installed. The problems would only start showing up once
you stated building. This is not very useful if you're cross-compiling
and trying to setup the paths correctly.
Reviewed-by: Denis
|
|
|