Porting guide?

I am considering porting a fairly large QNX 4.25 application to QNX 6. It is
a set of tasks, some of which are Photon based, and some of which are not. I
recall that there was a porting guide somewhere for this purpose, but I
can’t seem to find the reference. If anyone could point me at it, I would
appreciate it. Any comments on how hard or easy this porting job may be
would also be appreciated. Feel free to email me directly if you prefer.

Thanks,

Kevin
kevin.miller@transcore.com

Kevin Miller <kevin.miller@transcore.com> wrote:
KM > I am considering porting a fairly large QNX 4.25 application to QNX 6. It is
KM > a set of tasks, some of which are Photon based, and some of which are not. I
KM > recall that there was a porting guide somewhere for this purpose, but I
KM > can’t seem to find the reference. If anyone could point me at it, I would
KM > appreciate it. Any comments on how hard or easy this porting job may be
KM > would also be appreciated. Feel free to email me directly if you prefer.

KM > Thanks,

KM > Kevin
KM > kevin.miller@transcore.com

Here’s my $0.02. Don’t just port.

Take the little extra effort to re-design for QNX6. Take advantage of
threads where they make sense.

IPC is deffinitely different in QNX. It IS more difficult, regardless
of what anyone else may tell you. But since it is the new standard,
just get used to it and use it. Write a few test programs before you
even begin trying to redesign for QNX6.

If you try to shoe-horn a QNX4 design into QNX6 your cheating yoursef.
The overhead of QNX6 is significantly greater. So you may as well take
advantage of what your paying extra for.

Good luck.

Bill Caroselli wrote:

IPC is deffinitely different in QNX. It IS more difficult, regardless
of what anyone else may tell you.

Doing IPC is straightforward enough, but setting up for
message passing is surprisingly difficult. Directory services
are lacking or broken. name_attach doesn’t work across the
network in QNX 6.2, and spawn across the network has some
major bugs. (I’ve detailed all this in previous postings.)

Everything associated with making a stream-oriented “resource
manager” works reasonably well, but support for true message
passing is weak. This is sad, because message passing is
QNX’s greatest strength.

How much of this is fixed in QNX 6.3?

John Nagle
Team Overbot

How much of this is fixed in QNX 6.3?

With 6.3.0 people can go back to name_attach() and have network aware
name lookup with the gns (globle name server). No root access required.

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Ah, good. That was needed.

John Nagle



Chris McKillop wrote:

How much of this is fixed in QNX 6.3?



With 6.3.0 people can go back to name_attach() and have network aware
name lookup with the gns (globle name server). No root access required.

chris