Best location for redefining JAMSHELL

[mapiri]

Hi

we have tried to redefine JAMSHELL in site-config.jam, but it doesn't work. Redefining it in e.g. tools/gcc.jam does work, but since it is not gcc specific we would prefer to redefine in a more "global" location or even better, simply passing it as an argument to the b2 call, e.g. b2 -sJAMSHELL=my_jamshell_wrapper, but this also doesn't seem to work.
Any suggestions are welcome.

Thanks,
LS

[psandana]

@grafikrobot can you help us with this?

[grafikrobot]

AFAICT you can do this in your site-config.jam or user-config.jam:

using gcc ; # However you set up your gcc toolset.

import modules ;
modules.poke gcc : JAMSHELL : "/custom/shell %" ;

Which will replace the hard-wired value in gcc.jam after it's set from the using gcc ;.

Having said that.. It's totally wrong that gcc.jam is hard setting JAMSHELL.

[psandana]

I also noticed this yesterday. Thanks. We can use it for now. Shall we create an issue for this?

[grafikrobot]

Would certainly appreciate if you create an issue.

[mapiri]

So, for the time being, this would need to be done for any toolset (compiler) for which we want to support distributed compilation, correct?

[grafikrobot]

So, for the time being, this would need to be done for any toolset (compiler) for which we want to support distributed compilation, correct?

@mapiri no. GCC is the only that hard sets the JAMSHELL. All other toolsets just use the default JAMSHELL value.

PS. If you have multiple gcc toolsets configured (i.e. multiple using gcc invocations) you only need to reset the JAMSHELL only once. Not sure what to do if you need multiple different JAMSHELL values for each different gcc though.