From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-11-09 00:14:44
Sergey Nik wrote:
> Yes. I _don't know what the exact platform behavior is_.
> I suspect you should know more about as an expert in build tools.
> What I know exactly that when you build cross-tool for specific
> platform, you also build the bintools for that platform.
> And when you run "ar" from command line the following output can be seen:
> example for Mgw
> ar: supported targets: pe-i386 pei-i386 elf32-i386 elf32-little
> elf32-big srec symbolsrec tekhex binary ihex
> example for arm-linux
> arm-linux-ar: supported targets: elf32-littlearm elf32-bigarm
> elf32-little elf32-big srec symbolsrec tekhex binary ihex
Sure... But the logic that gcc.jam uses to determine which "ar" to use
goes something like this:
1. Use the ar program specified in the <archiver> option.
2. Use the "ar" program in the bin directory of the given g++.
3. Use the "ar" program in the system search path.
So if you use the common cross-compile setup of building binutils into a
tree localized for the specific target machine, i.e. in which you would
have a bin/ar and bin/g++, BBv2 would automatically work with a simple:
using gcc : : /path/to/arm-linux-cross-gcc/bin/g++ ;
Anything other than that requires that you tell BBv2 what the
non-standard name for the various programs is. As anything else would
require reading the users mind. And sadly, we don't have access to that
kind of hardware and software.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
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