In article <a5l8gp$p3i$1@inn.qnx.com>, brownr@aecl.ca says…
Like you we use Watcom 10.6 on Windows to cross compile for QNX4. There are
some many more tools available for the Windows platform that it just makes
good sense for us. We love QNX but lets face it they can’t compete tool wise
(yet).
Yep, most definately. That is why I originally set up my cross
compilation environment because I was so unproductive trying to edit,
compile and debug on my QNX4 box directly. Once I got myself set up with
a Windows cross compiler (very easy once you know how!) I was happily
editing in my favorite editor (SlickEdit), compiling in the same editor
and starting the TCP/IP remote debugger from the same editor. SlickEdit
has become my IDE of choice and allows me to compile with any compiler
all within the same IDE. ie: I can switch between Borland, Microsoft,
Watcom, GCC and other compilers and compile for DOS, OS/2, Windows,
Linux and QNX all from the same environment!
Perhaps one of these days I should post my macro package and
instructions on how to set this up, because once you have SlickEdit set
up this way it is very powerful (note that it does require a good
external command line make package such as our dmake to make it work
well).
We are now just starting down the QNX6 path and we wanted to maintain our
Windows development host so we purchased the QNX6 SDK for Windows. But
developing on Windows for so long meant we had come accustomed to IDEs and
GUIs wrappers for most tools. Since the QNX6 SDK is all command line tools
and doesn’t include an IDE we decided to purchase Metrowerks. The only
reason we purchased Metrowerks was to get the IDE. Quite a price tag for an
IDE.
So the Metrowerks IDE is really just an IDE that allows you to compile
QNX6 binaries using GCC, right? Is there a special IDE you need to buy
to get this (from QSSL?) or do you simply buy the commercial Metrowerks
IDE from them and then stuff in the Win32 SDK tools from QNX?
I know real programmers don’t use IDEs - we have become soft, look away
I am ashamed.
Actually I am a big fan of IDE’s because I do believe the increase
productivity. I still do all my compiling from the command line and
maintain my makefiles manually, but I do all my editing and compiling
from SlickEdit. You simply can’t beat a good editor/IDE that can do
source file tagging and cross referencing as well as giving you the
ability to compile within an IDE and instantly get to errors output from
the compiler. Besides, to me a good editor environment like SlickEdit
(and Emacs!!) is really a compiler independant IDE 
I would love to see OpenWatcom support for both QNX4 and QNX6 but as Rennie
often points out standards are always a concern. QNX4 has no other choice
but Watcom so they will take what they can get. QNX6 is a different story,
if OpenWatcom does match or surpass GCC with respect to standards then it
may not get much use even if it was supported on QNX6.
Standards are definately a concern for all of us who use Watcom on a
regular basis, and I do believe that once we finally get the source code
released there will be a lot of people willing to put in the effort to
make Open Watcom better (as well as complete the ports to MIPS and
PowerPC processors .
Regards,
–
±--------------------------------------------------------------+
| SciTech Software - Building Truly Plug’n’Play Software! |
±--------------------------------------------------------------+
| Kendall Bennett | Email: KendallB@scitechsoft.com |
| Director of Engineering | Phone: (530) 894 8400 |
| SciTech Software, Inc. | Fax : (530) 894 9069 |
| 505 Wall Street | ftp : ftp.scitechsoft.com |
| Chico, CA 95928, USA | www : http://www.scitechsoft.com |
±--------------------------------------------------------------+
