Re: [boost] [build] Algorithm for setting PATH when a 'run' or 'run-fail'

Subject: Re: [boost] [build] Algorithm for setting PATH when a 'run' or 'run-fail'
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-08-17 04:18:13

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Edward Diener
> Sent: 12 August 2015 01:16
> To: boost_at_[hidden]
> Subject: Re: [boost] [build] Algorithm for setting PATH when a 'run' or 'run-fail'
> 
> On 8/11/2015 2:33 PM, Edward Diener wrote:
> > What is the algorithm for setting a PATH on Windows when the 'run' or
> > 'run-fail' rule occurs in a jamfile ?
> >
> > In running clang on Windows when an executable is created the PATH
> > needs to start with the bin directory of the mingw(-64)/gcc
> > implementation that a particular version of clang uses as its RTL when
> > the program is compiled/linked. It appears that when the 'run' or
> > 'run-test' rule occurs with the clang toolset on Windows that the PATH
> > is adjusted to have the directory of the clang++ executable and not
> > that of the corresponding mingw(-64)/gcc RTL ? Is there any solution
> > to this from within Boost Build ?
> 
> I figured this out. Please ignore.

Maybe you could share your solution with us.  I have a problem using Clang that might be caused by
this.

Thanks

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]