Qt-interest Archive, September 2002
Reason for MAC and Windows mkspecs in LINUX Open Edition?
Message 1 in thread
Hi,
I wonder why the following mkspecs are included in QT 3 Open Edition for
LINUX:
win32-borland/
win32-g++/
win32-msvc/
win32-visage/
win32-watcom/
mac9-mwerks/
macx-g++/
macx-mwerks/
macx-pbuilder/
What will happen when I try to compile QT 3 under Windows or MAC-OS using
these specs?
Felix
Message 2 in thread
> I wonder why the following mkspecs are included in QT 3 Open Edition for
> LINUX:
> win32-borland/
> win32-g++/
> win32-msvc/
> win32-visage/
> win32-watcom/
> mac9-mwerks/
> macx-g++/
> macx-mwerks/
> macx-pbuilder/
Just because there was no good reason for somebody to spend time and remove
them. They aren't big, you know -- no space wasted.
> What will happen when I try to compile QT 3 under Windows or MAC-OS using
> these specs?
It will not compile as long as these platforms are not supporting x api
natively. Which probably will never happen.
Cheers, Kuba Ober
Message 3 in thread
On Friday 20 September 2002 03:25 pm, Kuba Ober wrote:
> It will not compile as long as these platforms are not supporting x api
> natively. Which probably will never happen.
Out of curiosity, wouldn't it be possible to link the QT Library with eg. the
XFree libraries and use a Windows X Server, eg. the one from MicroImages, to
run programs?
Felix
