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
*	Lighthouse on OS X.	Morten Johan Sørvig	2010-10-20	1	-1/+1
\| \| \| \|	Reviewed-by: Jørgen
*	Say hello to Qt for Native Client.	Morten Johan Sørvig	2010-05-14	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	This commits adds build system to support for the native client compiler (x86-only for now), sets up global defines, and adds compile fixes for QtCore and QtGui. Details: * Add mkspecs for linux-nacl-g++ and macx-nacl-c++ * Add nacl configure option * Add qconfig-minimal-system-dependencies.h * Define Q_OS_NACL in qglobal.h * Add qnacalunimplemented.h/cpp with POSIX stubs. * .pro file changes for cross-compiling on Mac
*	Use LIBS_PRIVATE on Mac and X11.	Thiago Macieira	2009-08-17	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Long live Qt!	Lars Knoll	2009-03-23	1	-0/+4