Path: utzoo!attcan!uunet!cs.utexas.edu!news-server.csri.toronto.edu!white.toronto.edu!ghfeil
From: ghfeil@white.toronto.edu (Georg Feil)
Newsgroups: comp.realtime
Subject: Re: compilers
Keywords: SunOS, native
Message-ID: <1990Jul11.125815.18182@jarvis.csri.toronto.edu>
Date: 11 Jul 90 16:58:15 GMT
References: <15290002@hpvcfs1.HP.COM> <2881@zipeecs.umich.edu> <1384@hslrswi.UUCP>
Organization: CSRI, University of Toronto
Lines: 34

In article <1384@hslrswi.UUCP> teape@hslrswi.UUCP (Andrew Kiggins) writes:
>hello,
>...according to the VxWorks blurb we can use the native compiler
>from SunOS 4.0 to do our compilation for the target, the Velocity blurb
>implies that we need a cross-compiler, and I'm afraid I can't tell the
>difference ( apart from $6,500 )...


You can definitely use the Sun native compiler with VxWorks, as well as
the GNU ANSI C compiler gcc (free software foundation). I do this every day.

I don't use Ready Systems/Velocity, but I have here a blurb on RTsource,
their source-level debugger, which has in it:

  " Use with the Sun-3 native C compiler and assembler; or with the Green
    Hills/Oasys C compiler and assembler. "

This seems to imply that the Sun native tools will work OK, but I'd check with
Ready Systems to make sure. Usually the source-level debugger is the component 
which decides which compilers will work, since it must read debugging 
information embedded in the object/executable files. 
As an example, pSOS+ from Software Components Group has a source-level 
debugger called XRAY+ that works only when a C compiler from Microtec is 
used (at a purchase cost of several thousand dollars).

Hope this helps,

Georg.
--
Georg Feil                                 Internet: ghfeil@white.toronto.edu
                                             -or-  : georg@sgl.ists.ca
..if all else fails, try:
{uunet,pyramid,watmath,utzoo}!utcsri!white!ghfeil      (UUCP)
ghfeil%white.toronto.edu@relay.cs.net                  (ARPA)