Igor, thanks for comments.
I’m used to QSSL marketing bubbles, but problem is, what to tell to
newbies when they look for orientation in that chaos when there are even
contrary announcements the same day… ?
Before deciding for a solution under a new OS or just starting with it
you will normally know what’s the future or what is to expect in a long
run with it…
Our customers dislike adventures or never boring dynamical OSes with
pre-programmed surprises… unfortunately they are looking for reliable
statements … ![:frowning: :frowning:](/images/emoji/twitter/frowning.png?v=9)
Jutta
Igor Kovalenko wrote:
Jutta, you need to learn to take marketing announcements a bit less
literally > ![:wink: :wink:](/images/emoji/twitter/wink.png?v=9)
Here is summary of what my fellow gipsy told me about next release:
- it will indeed be based on Dinkum libraries;
- it will be self-hosted on x86, just as now;
- other architectures will be supported by cross-development from x86
version;
- Metaware has little to do with next release;
- it does not matter what they call it, 6.1 or 6.0.1. They’re probably
not sure themselves;
Big difference is, you won’t have to buy QNX4-based SDK or
Metrowerks/Metaware to experiment with non-x86 systems, since 6.1 will have
its own cross-environment for them. However Metaware might be useful since
they (unlike Metrowerks) apparently have their own compiler and it might be
better than GCC for embedded systems.
I know they are working on many improvements and fixes as well, but don’t
want to second guess which ones will actually go into release. Things that
most certainly will be updated/fixed are QNET and NFS.
“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3AF41617.E18EAA0F@web.de> …
Markus Loffler wrote:
“Igor Kovalenko” <> Igor.Kovalenko@motorola.com> > wrote in message
news:> 3AF30156.CBF3E32E@motorola.com> …
I don’t know what happened then. AFAIK they are working on 6.1 release
so may be they don’t want another patch…
This actually would make sense. If you put in features, you’d need to
apply
bug fixes to the old version and the new version, which is a big pain…
So hope you’re right Igor and we get some fresh 6.1. update with a lot
of bugs fixed soon. ^^^^^^
At > http://www.qnx.com/news/pr/apr09_01-multi.html
from April 9th, 2001 is written:
“Embedded developers can now target multiple processor families
with less effort and less recoding thanks to the expanded
processor support of the QNX RTOS v6. […] General
availability of the QNX RTOS v6 is scheduled for June 2001.
^^^^^^^^^^^^
The QNX RTOS is a core component of the QNX realtime
platform, a complete, SELF-HOSTED DEVELOPMENT environment
that is available free of charge for non-commercial use…”
Did I understand correct that the June 2001 version is a self hosted
version for all supported processors?
What about an other release at the SAME DAY:
http://www.qnx.com/news/tpnews/apr09_01-meta.html > ??
How does the CROSS DEVELOPMENT of MetaWare fit to the announced
July 2001 QNX RTOS v.6 version?
Just YESTERDAY I got info from an US customer who has talked with
QSSL support. The Support told him that they will include another
compiler in their next release … and that the Next release of
QNX RTP (6.0.1) will incude the Dinkum C/C++ libriaries."
^^^^^^
Hmmm… at > http://www.qnx.com/news/pr/sep12_00-Dnkw.html > is written
on Sept.12th, 2000:
“The Dinkumware C and C++ libraries will be available in the
fourth quarter of this year as part of the QNX realtime platform.”
Is anyone from QSSL able or willing to inform the users a month
before June what will be the correct release name (QNX RTOS v6.x.x)
of the June 2001 version (whatever month it will be in Ottawa > ![:wink: :wink:](/images/emoji/twitter/wink.png?v=9)
and what will be removed or will be included ???
Sorry, I’m really a little bit confused.
Jutta