6.3.0 compatibility

We currently have x86 hardware in the field running QNX 6.2.1B. It’s a
fairly minimal embedded installation (no Photon, no Qnet). We do use the
filesystem, inetd, mqueue, and devc-ser8250.

Are there compatibility issues with running programs built in a 6.3.0
development environment on a box with a 6.2.1B boot image?

-Lisa Scanlan
Ormec Systems

Lisa Scanlan <~~~lscanlan@ormec.com> wrote:

We currently have x86 hardware in the field running QNX 6.2.1B. It’s a
fairly minimal embedded installation (no Photon, no Qnet). We do use the
filesystem, inetd, mqueue, and devc-ser8250.

Are there compatibility issues with running programs built in a 6.3.0
development environment on a box with a 6.2.1B boot image?

I don’t know of any off the top of my head, but I suspect you will
run into some issues. What is your development host? If you are using
Windows you can actually install the 6.3.0 tools along side of your
6.2.1 tools and build for 6.2.1 from the command line or 6.3.0 IDE without
any trouble.

chris

\

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

We’ve bumped into one particular compatibility problem several times: if you
compile a program under 6.30 and try to run it in a 6.2 environment, and that
program uses any of the err/warn family of functions, then you get a message
saying “unknown symbol: xxx Could not resolve all symbols” and the program
fails to run.

Murf

Lisa Scanlan wrote:

We currently have x86 hardware in the field running QNX 6.2.1B. It’s a
fairly minimal embedded installation (no Photon, no Qnet). We do use the
filesystem, inetd, mqueue, and devc-ser8250.

Are there compatibility issues with running programs built in a 6.3.0
development environment on a box with a 6.2.1B boot image?

-Lisa Scanlan
Ormec Systems

Lisa Scanlan <~~~lscanlan@ormec.com> wrote:

Thanks for the answer. Yes we are developing Windows-hosted. For
command-line building, is there anything similar to “Rebuild All” or do I
need to issue individual make commands for each project? We are using the
recursive makefile system that the IDE creates by default.

If you’ve got several projects, you’d have to write a little script,
or little makefile at the workspace level that goes into each project,
and issues a “make clean all” for each of them.

-David

Please follow-up to newsgroup, rather than personal email.
David Gibbs
QNX Training Services
dagibbs@qnx.com

Thanks for the answer. Yes we are developing Windows-hosted. For
command-line building, is there anything similar to “Rebuild All” or do I
need to issue individual make commands for each project? We are using the
recursive makefile system that the IDE creates by default.

“Chris McKillop” <cdm@qnx.com> wrote in message
news:cchudd$e4b$1@inn.qnx.com

Lisa Scanlan <~~~> lscanlan@ormec.com> > wrote:
We currently have x86 hardware in the field running QNX 6.2.1B. It’s a
fairly minimal embedded installation (no Photon, no Qnet). We do use
the
filesystem, inetd, mqueue, and devc-ser8250.

Are there compatibility issues with running programs built in a 6.3.0
development environment on a box with a 6.2.1B boot image?


I don’t know of any off the top of my head, but I suspect you will
run into some issues. What is your development host? If you are using
Windows you can actually install the 6.3.0 tools along side of your
6.2.1 tools and build for 6.2.1 from the command line or 6.3.0 IDE without
any trouble.

chris

\

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