| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
otherwise the build fails if the libraries are statically built, as glu
depends on opengl.
Task-number: QTBUG-11863
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset provides the basis for targetting win32-g++ on Unix using
the configure shell script:
support added to the configure script itself
support added to relevant config.tests
support added to mingw makefile generator in qmake
new makespec: unsupported/win32-g++-cross
The makespec is based on the win32-g++ makespec.
Merge-request: 2407
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
| |
Reviewed-by: joerg
|
|
|
|
|
|
|
|
|
|
| |
the unix makefile generator can make files for "regular" unixes and
macos (the difference being the framework handling). so far, the output
choice was hard-wired to the host platform. the previous commit made
that soft-configurable, and this one exploits this capability to enable
limited cross-building.
Reviewed-by: mariusSO
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
| |
Task-number: QTBUG-7683
Reviewed-by: Tom Cooksey
|
|
|
|
|
|
| |
POSIX header incorporates previously refactored X/Open LFS extensions.
Reviewed-by: Thiago Macieira
|
|
|
|
| |
Reviewed-by: Thiago Macieira
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
bin/syncqt
doc/src/deployment/deployment.qdoc
src/corelib/io/qfsfileengine_win.cpp
src/corelib/xml/qxmlstream.cpp
src/opengl/gl2paintengineex/qpaintengineex_opengl2_p.h
tools/assistant/tools/assistant/centralwidget.cpp
tools/linguist/lupdate/main.cpp
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
examples/webkit/fancybrowser/main.cpp
src/opengl/gl2paintengineex/qpaintengineex_opengl2.cpp
tools/assistant/tools/assistant/bookmarkmanager.cpp
|
| |
| |
| |
| | |
Reviewed-By: Trustme
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
src/corelib/io/qfsfileengine.cpp
src/network/access/qnetworkrequest.cpp
tests/auto/qgraphicswidget/tst_qgraphicswidget.cpp
|
| |
| |
| |
| | |
Reviewed-by: Harald Fernengel
|
|/
|
|
|
| |
Merge-request: 1875
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|\ |
|
| |
| |
| |
| | |
Fix a typo, update the tmp path to match current qws behavior.
|
|/
|
|
|
|
|
| |
In platforms with Large File Support, we use mmap64, to be able to
handle offsets (and therefore files) larger than 2Gb.
Reviewed-by: Thiago Macieira
|
|
|
|
|
|
|
|
| |
Documented that pkg-config functionality must be forced if used in
conjunction with this mkspec, and that PKG_CONFIG_PATH is a shell variable
not a qmake variable.
Reviewed-by: Anders Bakken <anders.bakken@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
Scratchbox 2 abstracts away toolchain considerations when cross compiling,
allowing us to introduce a generic scratchbox 2 mkspec. See blog for more
details:
http://labs.trolltech.com/blogs/2009/09/10/cross-compiling-qtx11
Reviewed-by: Anders Bakken <anders.bakken@nokia.com>
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
| |
This makes Qt work on QNX 6.4.
* no q3support, no phonon
* no QSharedMemory, no QSystemSemaphore, no QProcess
Reviewed-By: Robert Griebl
|
|
This makes Qt work on VxWorks 6.6+ in native (kernel) mode.
* compiles with the WindRiver GNU toolchain (Linux only)
* works with QWS (tested with the VNC driver only)
* tested on PPC hardware and the x86 VxWorks simulator
* no q3support, no phonon, no webkit
* no QSharedMemory, no QSystemSemaphore, no QProcess
* only one QApplication instance (flat address space)
* filesystem support depends heavily on the quality of the native driver
* QLibrary is just a dummy to make plugins work at all
* qmake transparently creates VxWorks munching rules for static ctors
* made auto-test cope with missing OS features
A special note regarding the Q_FOREACH patch for dcc:
when calling foreach(a,c) with c being a function returning a container,
the compiler would generate 5 references to some labels (.LXXXX), which
are not there (so the linker complains in the end).
Seems like dcc doesn't really like the 'true ? 0 : <function call to get type>'
statement
Reviewed-By: Harald Fernengel
|