|
|
|
The port goes through several steps. The most import step seems to us in porting the gui related code, followed by the io classes with cygwin mount table support and the network and printer stuff. At last the mingw/msvc based build system will be ready.
1. Project start
- Stage 1 - port the basic Qt class needed for using the native win32 gui (by Holger Schröder)
Milestone 1 - a cygwin hosted gpl'ed native Qt 2 library using the win32 gui is available -> reached
- Stage 2 - integrate the classes into a recent cygwin based qt3 release (by Richard Lärkäng, Ivan Deras and others)
Milestone 2 - a cygwin hosted gpl'ed native Qt 3 library using the win32 gui is available -> reached
- Stage 3 - port the io classes needed for using the native win32 io subsystem -> reached
- Stage 4 - set up a non cygwin based build system (mingw and msvc support done by the wolfpack project maintainers (http://wpdev.sf.net) -> reached
- Stage 5 - port process, network, printer and other classes needed for using the native win32 network subsystem -> reached
Milestone 3 - a cygwin or mingw/msvc hosted gpl'ed native Qt 3 library is available -> reached
- Stage 6 - upgrade to recent Qt release (3.3)
Milestone 4 - a recent cygwin or mingw/msvc hosted gpl'ed Qt 3 library is available -> reached
TODO
- port additional Qt application (some possibly applications may be listed on trolltechs application index)
- Fix outstanding bugs
- Make kdelibs4 work with Qt4/win32 :)
|
