supported, "ISO Standard" C++ compiler for QNX4?

QNX Newsgroups (Archives) qdn.public.qnx4.devtools
1

Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for things like
namespace, c++ casts, int64, etc…)?

Are there any plans to move to 11? (I see on www.openwatcom.com something
about patch 11.0c being made available to “current customers”, which I
assume means QSSL.)


peace!

2

Previously, citizenDAK wrote in qdn.public.qnx4.devtools:

Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for things like
namespace, c++ casts, int64, etc…)?

Are there any plans to move to 11? (I see on > www.openwatcom.com > something
about patch 11.0c being made available to “current customers”, which I
assume means QSSL.)

My understanding is that QSSL made the decision to move to gcc some time ago, before Watcom went open source. I asked a similar question a few months ago and found that some QSSL employees were reluctant to discuss the issue. Apparently there are some legal and marketing complexities raised by Watcom’s decision to go open source (either that, or everybody was in a bad mood because it was Mascot Day at QSSL headquarters - rumor has it they all had to dress up like giant neutrinos). :wink:

Also, this forum is generally reserved for technical discussions…

\

  • Pete



    I don’t work for QSSL.
3

Pete DiMarco <peted.NOSPAM@NOSPAM.ifspurity.com> wrote in message
news:Voyager.010112120336.162B@node1…

Previously, citizenDAK wrote in qdn.public.qnx4.devtools:
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for things
like
namespace, c++ casts, int64, etc…)?

Also, this forum is generally reserved for technical discussions…

  • Pete

I thought this was a good Development Tools Question.

Though quite frankely I’ve given up hope of ever seeing any new development
tools for QNX 4.

4

In article <93o45p$rb8$1@inn.qnx.com>, BC@SierraDesign.com (Bill at Sierra
Design) wrote:

Python?

Pete DiMarco <> peted.NOSPAM@NOSPAM.ifspurity.com> > wrote in message
news:Voyager.010112120336.162B@node1…
Previously, citizenDAK wrote in qdn.public.qnx4.devtools:
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for
things
like
namespace, c++ casts, int64, etc…)?

Also, this forum is generally reserved for technical discussions…

  • Pete

I thought this was a good Development Tools Question.

Though quite frankely I’ve given up hope of ever seeing any new
development
tools for QNX 4.
\

5

I have also asked about this and like others I didn’t get much response from
QSSL. Typically the way things work is by customer demand. If there was a
large group of QSSL users looking for Watcom 11.X on QNX4 then it might have
a chance but since most of the QNX4 users have migrated to NTO I think QNX4
is stuck with bug fixes and very limited new development.

Let’s hope I’m wrong, I would love to see Watcom 11.x for QNX4.

  • Richard

“citizenDAK” <please_reply_to_the@group.com> wrote in message
news:93nlqd$jej$1@inn.qnx.com…

Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for things
like
namespace, c++ casts, int64, etc…)?

Are there any plans to move to 11? (I see on > www.openwatcom.com > something
about patch 11.0c being made available to “current customers”, which I
assume means QSSL.)


peace!

6

There is still the Watcom 11.0 cross compiler that runs under DOS Windows.
Since that already supports QNX (We never had any problems with it),
I can’t imagine it would be insumountable to get a resident Watcom 11.0 compiler.
Comments?
-Paul

Brown, Richard <brownr@aecl.ca> wrote in message news:93up1l$q72$1@inn.qnx.com…

I have also asked about this and like others I didn’t get much response from
QSSL. Typically the way things work is by customer demand. If there was a
large group of QSSL users looking for Watcom 11.X on QNX4 then it might have
a chance but since most of the QNX4 users have migrated to NTO I think QNX4
is stuck with bug fixes and very limited new development.

Let’s hope I’m wrong, I would love to see Watcom 11.x for QNX4.

  • Richard

“citizenDAK” <> please_reply_to_the@group.com> > wrote in message
news:93nlqd$jej$> 1@inn.qnx.com> …
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for things
like
namespace, c++ casts, int64, etc…)?

Are there any plans to move to 11? (I see on > www.openwatcom.com > something
about patch 11.0c being made available to “current customers”, which I
assume means QSSL.)


peace!
\

7

Hi Paul,

Python 2.0 is available for QNX 4.25 and QNX RTP at
http://sourceforge.net/projects/pyqnx/
for all who like an OO interpreter language.

BTW, you will find additional a demo of PyDACHS, that’s Python with a
TRTD API extension, info at www.DACHS.net/PyDACHS_python-tilcon.htm

Regards,
Jutta


Paul McCormack wrote:

In article <93o45p$rb8$> 1@inn.qnx.com> >, > BC@SierraDesign.com > (Bill at Sierra
Design) wrote:

Python?


Pete DiMarco <> peted.NOSPAM@NOSPAM.ifspurity.com> > wrote in message
news:Voyager.010112120336.162B@node1…
Previously, citizenDAK wrote in qdn.public.qnx4.devtools:
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for
things like namespace, c++ casts, int64, etc…)?

Also, this forum is generally reserved for technical discussions…

  • Pete

I thought this was a good Development Tools Question.

Though quite frankely I’ve given up hope of ever seeing any new
development tools for QNX 4.
\

8

We’re already using Python.
We’ve even compiled Python into Apache for faster Support of Web Page Generation,
Including Armin’s Send/RTeceive/Reply SRR Extensions for sending amonst our
existing C Code.
Without being compiled into Apache, the Python does gave a performance hit
on Apache CGI-scripts as the Python interpreter has to be loaded into memory everytime,
whereas a compiled C program ran immediately.

-Paul


Jutta Steinhoff <j-steinhoff@web.de> wrote in message news:3A635238.51BA44D6@web.de…

Hi Paul,

Python 2.0 is available for QNX 4.25 and QNX RTP at
http://sourceforge.net/projects/pyqnx/
for all who like an OO interpreter language.

BTW, you will find additional a demo of PyDACHS, that’s Python with a
TRTD API extension, info at > www.DACHS.net/PyDACHS_python-tilcon.htm

Regards,
Jutta


Paul McCormack wrote:

In article <93o45p$rb8$> 1@inn.qnx.com> >, > BC@SierraDesign.com > (Bill at Sierra
Design) wrote:

Python?


Pete DiMarco <> peted.NOSPAM@NOSPAM.ifspurity.com> > wrote in message
news:Voyager.010112120336.162B@node1…
Previously, citizenDAK wrote in qdn.public.qnx4.devtools:
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for
things like namespace, c++ casts, int64, etc…)?

Also, this forum is generally reserved for technical discussions…

  • Pete

I thought this was a good Development Tools Question.

Though quite frankely I’ve given up hope of ever seeing any new
development tools for QNX 4.
\

9

Watcom 11.x cross compiler is hosted on various platforms such as MS DOS, MS
Win16, MS Win32 and OS/2 and a single host can create executables for every
target. The base package contains a few common libraries and then libraries
that are specific to each target. In order to build QNX4 you need the Watcom
11.x libraries specific to QNX4 and since these never got out of Beta I
don’t think users are legally allowed to build and ship Watcom 11.x QNX4
executables.

We use the Watcom 10.6 compiler hosted on NT to build QNX4 targets. In order
to do so though we had to purchase the base compiler from Sybase and the
QNX4 specifics from QSSL. Then we brought the QNX4 specific headers and
libraries across to the host platform.

We did switch to the 11.x base and specifics when the QNX4 11.x beta was
on-going but have since reverted when we heard that Beta died.

I never tried using the Watcom 11.x base with the Watcom 10.6 specifics of
QNX4 because I heard there were major differences that would not allow it to
work.

There is still the Watcom 11.0 cross compiler that runs under DOS Windows.
Since that already supports QNX (We never had any problems with it),
I can’t imagine it would be insumountable to get a resident Watcom 11.0
compiler.
Comments?
-Paul

10

“Paul Russell” <paul@jenosys.com> wrote in message
news:93vsld$h8g$1@inn.qnx.com…

We’re already using Python.
We’ve even compiled Python into Apache for faster Support of Web Page
Generation,
Including Armin’s Send/RTeceive/Reply SRR Extensions for sending amonst
our
existing C Code.
Without being compiled into Apache, the Python does gave a performance hit
on Apache CGI-scripts as the Python interpreter has to be loaded into
memory everytime,
whereas a compiled C program ran immediately.

Try starting the Python interpreter with on -h . That way one copy of
phyton will stay resident in memory in held state and will be reuse when
required.

-Paul


Jutta Steinhoff <> j-steinhoff@web.de> > wrote in message
news:> 3A635238.51BA44D6@web.de> …
Hi Paul,

Python 2.0 is available for QNX 4.25 and QNX RTP at
http://sourceforge.net/projects/pyqnx/
for all who like an OO interpreter language.

BTW, you will find additional a demo of PyDACHS, that’s Python with a
TRTD API extension, info at > www.DACHS.net/PyDACHS_python-tilcon.htm

Regards,
Jutta


Paul McCormack wrote:

In article <93o45p$rb8$> 1@inn.qnx.com> >, > BC@SierraDesign.com > (Bill at
Sierra
Design) wrote:

Python?


Pete DiMarco <> peted.NOSPAM@NOSPAM.ifspurity.com> > wrote in message
news:Voyager.010112120336.162B@node1…
Previously, citizenDAK wrote in qdn.public.qnx4.devtools:
Haven’t seen any recent news, so I was wondering:

Are we stuck with Watcom 10.6, (and must switch to RtP & gcc for
things like namespace, c++ casts, int64, etc…)?

Also, this forum is generally reserved for technical
discussions…

  • Pete

I thought this was a good Development Tools Question.

Though quite frankely I’ve given up hope of ever seeing any new
development tools for QNX 4.


\