From: Jim Douglas (jim_at_[hidden])
Date: 2005-11-06 07:09:41
Reece Dunn wrote:
> Jim Douglas wrote:
>>Reece Dunn wrote:
>>>Jim Douglas wrote:
>>>If I understand correctly, QNX6 uses a variant of the GCC compiler
QCC actually sits above gcc and calls gcc with the appropriate options
>>On the Windows cross-development platform QNX6 has gcc 2.95.3, gcc 3.3.5
>>and the Intel 8.1 compilers; it also had the appropriate (to the
>>compiler) GNU std lib and a universally available Dinkum std lib. So
>>selecting the desired combination is a must-have.
> Ok. I know nothing about the QNX6 platform. Are there any specific
> options you need to pass to the gcc and intel compilers to do the
> cross-compile and/or naming/location differences?
What I left out for simplicity's sake was that the QNX6 OS also runs on
various hardware platforms. The 'qcc/QCC' wrapper around the development
tools sorts out the fine detail mainly by using the "-V" option. A
couple of examples being:
(gcc ver 3.3.1, targeting PPC hardware, big-endian with Dinkum std lib)
(gcc ver 2.95.3, targeting x86 hardware with GNU std lib)
The only downside is that all "-W" & "-f" options have to be prefixed by
"-Wc," so that they are passed through to gcc.
I am still researching the Intel compiler...
>>>There is also support for BBv1 architecture, instruction-set and
>>>address-model in place, but they aren't currently used by the GCC toolset.
> ...so it is now possible (in BBv2) to say:
> bjam msvc-8.0 address-model=64
> to use the x86-amd64 cross-compiler that comes with VC8. The GCC stuff
> to process architectures hasn't (yet!) been ported.
Does this fit in with the above?
>>Who are the key players for BBv2?
> ... Rene (Rivera) knows a lot about bjam (upon which BBv1 and v2
> are built). Also, see the copyright notices on the various jam files.
> Also, for QNX6 support, a good place to start is to see how BBv1 does
Ah well, BBv1 support is still in the process of development - by me in
conjunction with Rene! I just thought I would get the ball rolling with
BBv2 because BBv1 is incapable of supporting cross compilation.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk