| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
