faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: QT/KDE on Cygwin
by Eric Laffoon on Saturday 14/Oct/2006, @04:51
|
I'm happily not involved in Windows coding, but I'm familiar with the projects. First of all it is not Qt not supporting Cygwin, it is the other way around. Cygwin typically lags behind the latest KDE releases. Beyond that I'm not sure if it ever will because the Qt4 windows package you are citing is a native GPL windows package. Cygwin provides X on Windows. Qt4 for windows is native AFAIK so that would mean no Cygwin. What Jaroslaw has been working on is KDE3 on Windows ported from Linux to Windows. KDE 4 will start off with a native windows GPL Qt.
This is similar to the Mac story where Fink (IIRC) was the library to run an X server on OS X and then a native GPL version of Qt was released. So if you're concerned about Qt/KDE on Mac and Windows introducing our software to people I'd say a lot more of them are going to be exposed if they don't have to set up an X server to run the software. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: QT/KDE on Cygwin
by S Page on Sunday 15/Oct/2006, @01:06
|
Yeah, I know Cygwin offers an X11 server (XOrg 6.8.99) on Windows, I'm not talking about that. I just wanted to build the Qt for Windows *source* code using the build tools that I've already installed under Cygwin (g++, GNU make, etc. in the Cygwin UNIX-like environment) rather than the MinGW tools (g++, mingw32-make, etc. in a DOS-like environment) Even though the commands are similar, I realize it's non-trivial to support both, e.g. configure output has
Build is done in............C:\cygwin\home\spage\qt-win-opensource-src-4.2.0
Install prefix............../home/spage/qt-copy
Headers installed to........\home\spage\qt-copy\include
Darn Windows path separators and drive letters! :-)
(I occasionally ran ranger rick's fine KDE 3/Fink work on a company Mac laptop.)
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|