[Info-vax] VMS Software Releases Roadmap Updates

[Jan-Erik Söderholm]

Den 2021-09-28 kl. 20:11, skrev Dave Froble:
> On 9/28/2021 1:36 PM, Simon Clubley wrote:
>> On 2021-09-27, Dave Froble <davef at tsoft-inc.com> wrote:
>>>
>>> I don't think it was the money.  Bill is a bit old fashioned, like me,
>>> and just feels the build tools should be native.
>>>
>>
>> You've never done any embedded work have you ? :-)
>>
>> Simon.
>>
> 
> No, I have not.

Note that, what Simon calls "embedded" today, it just the same kind
of development that was once done for VAXELN. You wrote, compiled
and linked your application on one system and then deployed on
another system. Your application booted directly without any
underlaying operating system.

That these two happend to have the same basic architecture (VAX)
is of no real importance.

Today, if you build apps for PIC, AVR or similar embedded platforms,
you write, compile and link on one system (usually a Windows laptop)
and deploy ("flash") on the target processors.

The differnce from IA64/x86 is that you compile on IA64 and link
on x86 (if I understand correctly, maybe it is both compile and
link on IA64?).

For what it matters, I could very well live with a cross-compile
environment for OpenVMS based on a Windows platform. That would
probably give much better code editing tools, anyway.
I do not know if that ever was an option for VSI, of course...

And yes, IA64 might look as a not so good choice today, but when
the x86 port begun, it was probably more reasonable.

And, as Arne has mentioned several time, this is just a temporary
solution that will go away during next year.


> But I knew that much of such development would not be on 
> the target platform.  No or few such tools on the dedicated HW.
> 
> General purpose computers are another world, and, I'm old fashioned, and 
> don't get out much.
>