Re: [Boost-build] Is it possible to override the CONFIG_COMMAND ?

Subject: Re: [Boost-build] Is it possible to override the CONFIG_COMMAND ?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-08-28 22:41:24

AMDG

On 08/28/2018 04:16 PM, Kuhl, Brian via Boost-build wrote:
> Our toolchain developers have decided to link with "ld" instead of "gcc"
> Propagating there cross-build gcc configuration to Boost jam environment is challenging.
> there <linkflags> don't have "-Wl," prefix
> 
> I'm considering a couple of options, but when I experiment with <linker> option in init()
> 
>     # - linker tool other than default gcc++
>     local linker = [ feature.get-values <linker> : $(options) ] ;
>     if $(linker)
>     {
>         toolset.flags gcc.link CONFIG_COMMAND $(condition) : $(linker[1]) ;
>     }
> 
> It's prepending instead of replacing ..

That's the standard behavior of flags.  You could
change the action to use $(CONFIG_COMMAND[1]), but
that's kind of hacky.

> ldppc -m elf64ppc --oformat=elf64-powerpc ccppc  -o  .....
> 
> How do I replace instead of prepend?
> Do I need to define a "generator"
> 

  Yes, you need to define a generator.  The
existing link action hard-codes the -Wl,
prefix, because it assumes that you are using
gcc to link.  There are already a couple
alternate linking generators for mingw and
cygwin.

In Christ,
Steven Watanabe