Previously, Markus Loffler wrote in qdn.public.qnxrtp.devtools:
NTO defines QNXNTO
Thanks, that is what I wanted to know – But where did you find this from… it is not in the help system at least by searching for QNXNTO
– it is not under qcc or gcc…
– now that I know what to look for I can find it in header files in /usr/include.
– OK it is the migration kit under the “Development Environment”
section - but you will find it only if you search for QNXNTO
QNXNTO finds nothing… then again if you knew to search for QNXNTO
you wouldn’t need to find it at all…
I know this is a just being released but this really should be documented in the help for the qcc or gcc… or at least a link from there to information in the migration kit. i.e a See Also
Watcom defines WATCOMC
GNU defines GNUC
NTO defines QNX
QNX defines QNX
so to test for QNX now you have to test if defined(QNX) &&
“AII Development” <> email@example.com> > wrote in message
I am just starting the conversion from QNX4 to Nto. For
my own sanity I am porting TCSH to Neutrino… - I don’t
feel like rewriting all my scripts for bash.
I have some basic questions regarding the changeover.
what is the NTO specific #define?
i.e. in QNX4 you could use QNX for QNX only code I would like to make
my code changes such that I can still compile under QNX4 –
Is there a general invocation to configure that should be used when
porting to NTO? I have gotten the latest config.guess and config.sub off the
gnu.org site – Now I get a “x86-pc-nto-qnx” system which is unsupported in
the configure script… I don’t have a problem adding that type to the
configure script - But I don’t want to add a non-standard machine… Should I
get a pre-ported app and see what someone else has done… if so what is the
Any other suggestions would be welcome