| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Updated version of LGPL and FDL licenseheaders.
Apply release phase licenseheaders for all source files.
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
RevBy: Trust me
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
examples/opengl/samplebuffers/glwidget.cpp
src/corelib/io/qfsfileengine_unix.cpp
src/corelib/kernel/qobject.cpp
src/corelib/tools/qsharedpointer.cpp
src/gui/gui.pro
tests/auto/qhttp/tst_qhttp.cpp
tests/auto/qkeyevent/tst_qkeyevent.cpp
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.exe
doc/src/classes/qnamespace.qdoc
examples/examples.pro
src/corelib/kernel/qcoreevent.cpp
src/corelib/kernel/qobject.cpp
src/gui/kernel/qapplication.cpp
src/gui/kernel/qstandardgestures.h
src/gui/kernel/qwidget.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Accept that we cannot do everything, so users using outdated
toolchains may have threading problems (leaking file descriptors).
It's not like this is a recent problem anyway...
Reviewed-By: Bradley T. Hughes
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
config.tests/unix/openssl/openssl.pri
demos/embedded/embedded.pro
examples/itemviews/chart/chart.pro
examples/network/network.pro
examples/painting/painterpaths/painterpaths.pro
examples/threads/mandelbrot/mandelbrot.pro
qmake/project.cpp
src/3rdparty/libtiff/libtiff/tif_config.h
src/corelib/arch/arch.pri
src/corelib/global/qglobal.cpp
src/corelib/kernel/kernel.pri
src/corelib/kernel/qcore_unix_p.h
src/corelib/kernel/qobject.cpp
src/corelib/thread/qthread_unix.cpp
src/corelib/tools/qsharedpointer_impl.h
src/corelib/tools/tools.pri
src/gui/kernel/qaction.h
src/gui/kernel/qapplication.cpp
src/gui/painting/qregion.h
src/gui/widgets/qlineedit.cpp
src/gui/widgets/qlineedit_p.h
src/network/socket/qnativesocketengine_unix.cpp
tests/auto/qdir/tst_qdir.cpp
tests/auto/qdiriterator/tst_qdiriterator.cpp
tests/auto/qhttp/qhttp.pro
tests/auto/qline/qline.pro
tests/auto/qnetworkreply/tst_qnetworkreply.cpp
tests/auto/qresourceengine/qresourceengine.pro
tests/auto/qsharedpointer/qsharedpointer.pro
tests/auto/qstring/qstring.pro
tests/auto/qtcpsocket/qtcpsocket.pro
tests/auto/qtcpsocket/tst_qtcpsocket.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is no monotonic clock support on HP-UXi at all, and the
_POSIX_MONOTONIC_CLOCK macro is not defined at all (not even to
-1). We handle this in the event dispatcher, but not in
qcore_unix.cpp. Since the monotonic clock time code has moved, the
define of _POSIX_MONOTONIC_CLOCK to -1 should also move.
Reviewed-by: thiago
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since these operators are also used by qcore_unix.cpp, it makes more
sense to have them in qcore_unix_p.h so that these files can be compiled
without a dependancy on the unix event dispatcher. Also remove some
headers from the unix event dispatcher since the headers are already
included in qcore_unix_p.h
Reviewed-by: brad <bradley.hughes@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Merge the monotonic clock source detection in
qeventdispatcher_unix.cpp with that in qcore_unix.cpp. As discussed
with Thiago, we're also removing older compat code at the same time
(spinning on select() when we think it woke up early).
Reviewed-by: Thiago
|
|/
|
|
|
| |
The ususal suspects like QScopedPointer fixes, but also some changes
since the introduction of qcore_unix.*
|
|
|
|
| |
Approach suggested by Rohan on 1866485e46039d51ea78a6d672b678aa02f68eef
|
|
|
|
| |
Reviewed-By: hjk <qtc-committer@nokia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes: corelib/kernel/qcore_unix_p.h:127: error: `O_CLOEXEC' undeclared
Some toolchains claim to provide glibc >= 2.4 but do not define
O_CLOEXEC.
An alternative fix might be to define O_CLOEXEC ourselves as we do
with some of the system call numbers.
|
|
|
|
| |
That's what unistd.h uses: void* can receive any pointer, while char* can't
|
|
|
|
| |
Reviewed-By: ossi
|
|
Most of these functions are from unistd.h and need to have a loop
around the actual call because the calls can be interrupted by a
signal delivery.
Some special calls (open, dup2, pipe) require an extra flag to support
thread-safe execution: the file descriptor must be created from the
operating system with the FD_CLOEXEC flag already set.
The O_CLOEXEC flag is specified in POSIX.1-2008, but the rest is
Linux-specific.
Reviewed-By: João Abecasis
|