Re: [Boost-build] [BBv2][QNX6] cross compilation of the libs on Windows

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2005-11-06 07:53:36

Jim Douglas wrote:
> Reece Dunn wrote:
> 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:
> 
> QCC -V3.3.1,gcc_ntoppcbe_cpp	
> (gcc ver 3.3.1, targeting PPC hardware, big-endian with Dinkum std lib)
> 
> QCC -V2.95.3,gcc_ntox86_gpp
> (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.

It may be better to create a new qcc.jam file that is based on GCC but 
doesn't extend it. That way, you can:
*  explicitly name the QCC tool;
*  avoid the issue of mixing GCC cross-compilation with QNX6 
cross-compilation;
*  deal with the -Wc, issue;
*  pass in the -V<version>,target option depending on the version 
specified and the platform targetted, e.g. for your examples above:

    using qcc : 3.3 ;
    using qcc : 2.95 ;

    $ bjam qcc-3.3 architecture=power stdlib=dinkum
    $ bjam qcc-2.95 architecture=x86 stdlib=default

However, you might want to take a look at the como-linux toolset that 
uses gcc as its backend and use that as a basis for the qcc tool.

HTH,
- Reece