Qt & CodeWarrior

Hi Ron,

I know that there's still a lot out there you cannot talk about, and
if this is included, just say so, but I am hoping not...  :-)

We are seriously considering using Trolltech's Qt as our new
cross-platform framework for an upcoming project, but as last I heard,
CodeWarrior was incompatible with the Qt source.  (Metrowerks blames
Qt for being incomaptible, Trolltech blames CodeWarrior for the same,
you know how that goes...)  I neither know nor care who is "at fault",
but my fear is that we will be forced to switch from CodeWarrior to a
dual XCode/Visual C++ compiler strategy to be able to use Qt.

So, I was wondering if Qt was one of the codebases planned to test
CodeWarrior 10 (CodeWarrior X?) when that comes out?  I'd love to be
able to stay with CWPro, but it looks increasingly likely that we will
be forced to switch based upon this issue alone.

If not, or you cannot answer that, I understand.  Then interpret this
as a gentle feature request.  :-)

Regards,

Jonathan Hoyle

In article <bc8cf544.0408051307.65905f7e@posting.google.com>,
jonhoyle@mac.com (Jonathan Hoyle) wrote:

>Hi Ron,
>
>I know that there's still a lot out there you cannot talk about, and
>if this is included, just say so, but I am hoping not...  :-)
>
>We are seriously considering using Trolltech's Qt as our new
>cross-platform framework for an upcoming project, but as last I heard,
>CodeWarrior was incompatible with the Qt source.  (Metrowerks blames
>Qt for being incomaptible, Trolltech blames CodeWarrior for the same,
>you know how that goes...)  I neither know nor care who is "at fault",
>but my fear is that we will be forced to switch from CodeWarrior to a
>dual XCode/Visual C++ compiler strategy to be able to use Qt.

The only problem I'm aware of is that Trolltech used a MS implementation
of a standard library that was wrong, but this wasn't that big of a
deal.  What problems are you having.

Contact me with more information.  I offered several times to work as a
middleman for Trolltech and basically got the impression they didn't
really care, but maybe I was talking to the wrong person.

Ron

--
Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
--   http://www.metrowerks.com/community  --

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

Are you saying it would be possible to use CodeWarrior + Qt on windows?

This questions has come up from Qt-newcomers almost once every month on the 
Qt mailing list in the last 6 months but is always left without reply.

CodeWarrior is not an option in the latest (3.3.3) Qt release on Windows. VC
++, Borland, MinGW and Watcom are the only ones.

In the Mac-release of Qt CodeWarrior is an option but Trolltech say it is un
supported. You also must know it exists - it is not mentioned in the documen
tation.

I'm sending an email to Qt support about this. I think I know the answer but
 at least I have added my vote.

/Jan L.

After talking to Trolltech it is apparent that CodeWarrior and Qt soon is a 
no-go. The curent unsupported Codewarrior-support will not be continued in Q
t 4.0.

jlarsson <jlarsson.1audts@mail.codecomments.com> wrote in message news:<jlarsson.1audts@mai
l.codecomments.com>...
> After talking to Trolltech it is apparent that CodeWarrior and Qt soon
> is a no-go. The curent unsupported Codewarrior-support will not be
> continued in Qt 4.0.

Which clearly shows their code is getting even less standard compliant
and portable with that new release <sigh>

Thorsten

> Which clearly shows their code is getting even less standard compliant
> and portable with that new release <sigh>

This is truly unfortunate.  However, Metrowerks' Windows compiler has
various options for you to set to be compatible with Visual C++, even
as far as using Microsoft's name-mangling protocols.  One would like
to believe a similar thing can be done on the Mac side to be
compatible with gcc/Xcode.  If so, then hopefully Qt would work with
Codewarrior as it currently does in Xcode.

quote:
Originally posted by Jonathan Hoyle 
> Which clearly shows their code is getting even less standard compliant
> and portable with that new release <sigh>

This is truly unfortunate.  However, Metrowerks' Windows compiler has
various options for you to set to be compatible with Visual C++, even
as far as using Microsoft's name-mangling protocols.  One would like
to believe a similar thing can be done on the Mac side to be
compatible with gcc/Xcode.  If so, then hopefully Qt would work with
Codewarrior as it currently does in Xcode. 
 

I dont think it is C++ incompatibilities that is the problem. 

It is the IDE-integration. I think I read in the Qt 4 info that they are wor
king to integrate Qt Designer more closely into VC++ and XCode. There should
 be no problem doing the same with CodeWarrior, they just dont see a market.
 They may already be behind schedule on the new Qt Designer, it was not incl
uded with the preview of Qt4.

As for me - I'm back running qmake, make and gcc on both win and mac. I like
 an environment that doesnt change and give trouble if I need to re-build a 
few years later ...

In article <jlarsson.1anwhm@mail.codecomments.com>,
jlarsson <jlarsson.1anwhm@mail.codecomments.com> wrote:

>Are you saying it would be possible to use CodeWarrior + Qt on windows?
>
>This questions has come up from Qt-newcomers almost once every month on
>the Qt mailing list in the last 6 months but is always left without
>reply.

Can you send me a URL to sign up for this list, or better yet to read it
online.

>CodeWarrior is not an option in the latest (3.3.3) Qt release on
>Windows. VC++, Borland, MinGW and Watcom are the only ones.

Wow they support compilers not made  for several years but not ours?  I
think maybe they just didn't update the list.

>In the Mac-release of Qt CodeWarrior is an option but Trolltech say it
>is unsupported. You also must know it exists - it is not mentioned in
>the documentation.
>
>I'm sending an email to Qt support about this. I think I know the
>answer but at least I have added my vote.

I'm sure we will work with Qt and it is just a matter of getting
engineers to talk to each other.    From the web site it looks like they
use makefiles and we should support the standard makefiles with our
command line tools on Windows and Mac.

Ron

--
Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
--   http://www.metrowerks.com/community  --

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

In article <jlarsson.1audts@mail.codecomments.com>,
jlarsson <jlarsson.1audts@mail.codecomments.com> wrote:

> After talking to Trolltech it is apparent that CodeWarrior and Qt soon
> is a no-go. The curent unsupported Codewarrior-support will not be
> continued in Qt 4.0.

Well since you talked to them, maybe you could share their reasons...

quote:
Originally posted by Sean McBride 
In article <jlarsson.1audts@mail.codecomments.com>,
jlarsson <jlarsson.1audts@mail.codecomments.com> wrote:

> After talking to Trolltech it is apparent that CodeWarrior and Qt soon
> is a no-go. The curent unsupported Codewarrior-support will not be
> continued in Qt 4.0.

Well since you talked to them, maybe you could share their reasons... 
 

Part of their answer below. I would guess
that Trolltech is not aware that CW is cross-
platform. The second answer to the question
if the unsupported CW-mode would remain
in Qt4.

"No problem as such, it is more of a priority 
issue within Trolltech.  We have decided to 
focus our efforts on Xcode instead of 
Codewarrior for now."

"There are no immediate plans to add Codewarrior
support. Since we never officially have supported
CW, we do not plan to support it unofficially
either."