Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update tech preview license header for files that are new in 4.6.	Jason McDonald	2009-08-31	8	-104/+104
\| \| \| \|	Reviewed-by: Trust Me
*	Update contact URL in license headers.	Jason McDonald	2009-08-12	8	-8/+8
\| \| \| \|	Reviewed-by: Trust Me
*	Fix obsolete license headers	Jason McDonald	2009-08-04	4	-8/+8
\| \| \| \|	Reviewed-by: Trust Me
*	Port of Qt to QNX	Harald Fernengel	2009-07-29	8	-0/+653
\| \| \| \| \| \| \| \|	This makes Qt work on QNX 6.4. * no q3support, no phonon * no QSharedMemory, no QSystemSemaphore, no QProcess Reviewed-By: Robert Griebl
*	Port of Qt to VxWorks	Robert Griebl	2009-07-29	8	-0/+549
	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