Hello,
one of our targets is still running QNX 6.2.1. How do I setup a QNX
6.3.0 Momentics projects to build for QNX 6.2.1? The main problem for me
seem to be the symbolic links for shared objects, which link to the
6.3.0 so’s versions (e.g. libph.so.3).
Any possibilities except relinking to the old so’s?
— Wolfram
What host are you using?
Under windows you can use the QWinCfg utility (Start Menu → Program
files → QNX Momentics → QWinCfg) to switch your development environment
between 6.3.0 and 6.2.1. (Note: In this example you must have 6.3.0 and
6.2.1 installed on your Windows Host).
If you are on a non-Windows host then you can use the qconfig utility (see
the utility reference for details).
Regards,
Joe
Wolfram Manthey <qnxnews@arcor.de> wrote in message
news:cp9m2b$fdt$1@inn.qnx.com…
Hello,
one of our targets is still running QNX 6.2.1. How do I setup a QNX
6.3.0 Momentics projects to build for QNX 6.2.1? The main problem for me
seem to be the symbolic links for shared objects, which link to the
6.3.0 so’s versions (e.g. libph.so.3).
Any possibilities except relinking to the old so’s?— Wolfram
Except that the QNX 6.2.1 IDE is almost unusable.
Joe Mammone wrote:
What host are you using?
Under windows you can use the QWinCfg utility (Start Menu → Program
files → QNX Momentics → QWinCfg) to switch your development
environment between 6.3.0 and 6.2.1. (Note: In this example you must
have 6.3.0 and
6.2.1 installed on your Windows Host).If you are on a non-Windows host then you can use the qconfig utility
(see the utility reference for details).Regards,
Joe
Wolfram Manthey <> qnxnews@arcor.de> > wrote in message
news:cp9m2b$fdt$> 1@inn.qnx.com> …
Hello,one of our targets is still running QNX 6.2.1. How do I setup a QNX
6.3.0 Momentics projects to build for QNX 6.2.1? The main problem
for me seem to be the symbolic links for shared objects, which link
to the
6.3.0 so’s versions (e.g. libph.so.3).
Any possibilities except relinking to the old so’s?— Wolfram
Robert Muil wrote:
Except that the QNX 6.2.1 IDE is almost unusable.
If you’ve installed 6.3.0 on a system that formerly had 6.2.1 on it, you
can switch the build environment around; you’ll be using the 6.2.1 libs,
etc. but the 6.3.0 IDE.
–
Chris Herborth (cherborth@qnx.com)
Never send a monster to do the work of an evil scientist.
That’s exactly what I want to do: build for and launch to a 6.2.1 target,
using a 6.3.0 Windows-hosted IDE (which has both 6.2.1 and 6.3.0 installed
on it). How do I set up my 6.3.0 IDE to build an executable that expects
libcpp.so.2 instead of libcpp.so.3? Or do I need to build it with the 6.2.1
IDE and then launch it using 6.3.0?
TIA
-Lisa Scanlan
“Chris Herborth” <cherborth@qnx.com> wrote in message
news:cpncr9$n86$1@inn.qnx.com…
Robert Muil wrote:
Except that the QNX 6.2.1 IDE is almost unusable.If you’ve installed 6.3.0 on a system that formerly had 6.2.1 on it, you
can switch the build environment around; you’ll be using the 6.2.1 libs,
etc. but the 6.3.0 IDE.–
Chris Herborth (> cherborth@qnx.com> )
Never send a monster to do the work of an evil scientist.
I’m also interested in the answer to this…
Lisa Scanlan wrote:
That’s exactly what I want to do: build for and launch to a 6.2.1
target, using a 6.3.0 Windows-hosted IDE (which has both 6.2.1 and
6.3.0 installed on it). How do I set up my 6.3.0 IDE to build an
executable that expects libcpp.so.2 instead of libcpp.so.3? Or do I
need to build it with the 6.2.1 IDE and then launch it using 6.3.0?TIA
-Lisa Scanlan
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:cpncr9$n86$> 1@inn.qnx.com> …
Robert Muil wrote:
Except that the QNX 6.2.1 IDE is almost unusable.If you’ve installed 6.3.0 on a system that formerly had 6.2.1 on it,
you can switch the build environment around; you’ll be using the
6.2.1 libs, etc. but the 6.3.0 IDE.–
Chris Herborth (> cherborth@qnx.com> )
Never send a monster to do the work of an evil scientist.
Hi,
To use the 6.3.0 IDE to build 6.2.1 target binaries:
Joe
Robert Muil <r.muil@crcmining.com.au> wrote in message
news:cprj0e$lu$1@inn.qnx.com…
I’m also interested in the answer to this…
Lisa Scanlan wrote:
That’s exactly what I want to do: build for and launch to a 6.2.1
target, using a 6.3.0 Windows-hosted IDE (which has both 6.2.1 and
6.3.0 installed on it). How do I set up my 6.3.0 IDE to build an
executable that expects libcpp.so.2 instead of libcpp.so.3? Or do I
need to build it with the 6.2.1 IDE and then launch it using 6.3.0?TIA
-Lisa Scanlan
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:cpncr9$n86$> 1@inn.qnx.com> …
Robert Muil wrote:
Except that the QNX 6.2.1 IDE is almost unusable.If you’ve installed 6.3.0 on a system that formerly had 6.2.1 on it,
you can switch the build environment around; you’ll be using the
6.2.1 libs, etc. but the 6.3.0 IDE.–
Chris Herborth (> cherborth@qnx.com> )
Never send a monster to do the work of an evil scientist.
Lisa Scanlan wrote:
That’s exactly what I want to do: build for and launch to a 6.2.1 target,
using a 6.3.0 Windows-hosted IDE (which has both 6.2.1 and 6.3.0 installed
on it). How do I set up my 6.3.0 IDE to build an executable that expects
libcpp.so.2 instead of libcpp.so.3? Or do I need to build it with the 6.2.1
IDE and then launch it using 6.3.0?
If you have 6.3.0 installed, never use the 6.2.1 IDE again (because the
one in 6.3.0 is significantly better).
From the “Window” menu, choose Preferences.
Click “QNX” in the left-hand pane of the prefs dialog.
Click the Select Install drop-down and choose 6.2.1
Then you’re building 6.2.1 executables and can download/run them through
the IDE’s launch configurations as normal on a 6.2.1 host (or a 6.3.0
host, actually).
Pretty sure this is documented in the 6.3.0 IDE User’s Guide, but it
might be something I added after I came on board (again)… those
changes won’t show up until Service Pack 1 ships (it’s in testing now).
–
Chris Herborth (cherborth@qnx.com)
Never send a monster to do the work of an evil scientist.