Thanks for your kind reply.
Most new applications, especially “realtime” or “control” type
aren’t usually done in X – it is mostly used for portability purposes.
That makes sense.
Everyone uses the GNU compiler – the GNU vs Dinkum is libraries. GNU
libraries are (IIRC) offered x86 only, and primarily, again, for
compatability with existing code that is being ported to QNX. (e.g.
for code in GNU/public applications where they depend on a particular
non-standard behaviour, or extension, in the GNU version of the library,
it can use the GNU libraries.) The default, and what is used by most
people, would be the Dinkum libraries.
What about gcc versions 2.95.3 vs 3.3.1
The reason I ask is there is a section in the helpviewer docs “/A Roadmap to
the QNX Mometics Professional Edition/6.30 and 6.21 Compatibility” that
mentions that the C++ libs and compilers…
libcpp.so.2 is for qnx 6.2.1
libcpp.so.3 is for 6.3.0 (compiled with GCC 2.95.3)
libcpp.so.4 is for 6.3.0 (compiled with GCC 3.3.1)
and I knew 2.95 had issues w/exceptions (I had problems with exceptions
using g++ but QCC -Vgcc_ntox86_cpp has no problems).
I guess it’s just different libs like you say.
I can’t comment on OpenGL vs Photon – don’t know enough about
OpenGL. (I think it is targeted at high-performance animation
type stuff, though.) It may not be an either-or, it may be
look at what you’re trying to do, and pick one vs the other.
There are supposed to be 2 implementations in QNX, Mesa and QNXGL. Both
implement some form of OpenGL (but I couldn’t find glut). The photon based
implementation is what I should use based on your feedback above re: photon
I would suggest pure Photon over X. As noted, the X in Photon is
primarily for portability and running things on the desktop.
Hope this helps a bit.
It’s been very helpful. I see all these 3rd party programs and libs etc. and
wonder how well supported and reliable they are under QNX. And I get all
excited but it looks like really not too much has changed since QNX 4.25,
if you want the reliable real-time apps you go with the QNX provided tools
and APIs. And reliability is why I’m using QNX for this project.
Thanks for your answers.