Re: Green Hills Ada library question (Ada on VxWorks)

[dewarr@my-dejanews.com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]

In article <6tu9n7$all$1@nnrp1.dejanews.com>,
  dennison@telepath.com wrote:
> In article <6tts7j$4hk1@news.kvaerner.com>,
>   "Tarjei Tj�stheim Jensen" <tarjei.jensen@kvaerner.no> wrote:
> >
> > dennison@telepath.com wrote in message
> > >What I would need is a PC-clone VxWorks port, which I note isn't in your
> list.
> > Linux might be an alternative to wxworks if your demands for real time are
not
> > excessive. There is said to be a RT version of Linux, but its quality is
> > unknown to me.
> >
>
> They are. We have to be scheduled reliably with minimal jitter at 240Hz, I
> believe. The point wasn't that I'm looking for a RTOS, though. We are way
past
> that point. We are almost past the point where we can change compilers. I was
> just wondering who else has tried to build a large system using Green Hills
> AdaMulti, and  how they dealt with the tools.
>
> With their tools, there seems to be no way to create scripts to "register" a
> new system with the library. It has to be done *manualy* with the GUI, or by
> reverse-engineering their build files and using external tools (like TCL).
> The only reasonable solution I can see is to create hierarchal levels of
> build files and maintain them in the revision system with the source code.
> That makes it the developer's responsibility to maintain the build files.
>
> Of course these files have to be created the first time. That means I have to
> sit down with the mouse and make 42 of these files containing all 371 units.
> Carpel-tunnel here I come!
>
> --
> T.E.D.
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum


Incidentally: the reason that I said that PC-Clone was a
somewhat odd designation for an embedded system is that
at the bare board level, PC clones can have substantial
differences. These are masked when using some Microsoft
OS, since one of the things an OEM does is to provide
interfaces for implementation specific aspects of a
particular board.

So usually you want to be a bit more precise in designating
the target if you are building an embedded system. For
example, there is no such thing as a completely generic
TCP-IP ethernet interface at this level, the details will
depend on what particular ethernet card you are using.

Robert Dewar

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum