Re: [boost] [modular-boost] "b2 headers" behavior on Windows

Subject: Re: [boost] [modular-boost] "b2 headers" behavior on Windows
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2014-02-03 19:44:26

Vyacheslav Andrejev <mortituris <at> mail.ru> writes:

> 
> Hello Gennadiy,
> 
> GR> I do not really want to delve into details of our makesystem.
> 
> But you can try to change a couple of symbols in the file I pointed you 
to. 
> It doesn't hurt to try, right?

It does. I am not familiar enough with Boost.Build syntax and in no position 
to learn it. Regardless I was looking for someone who IS familiar with it to 
make the change everybody can use.
 
> GR> Really? I did not know that. I used junction.exe and Far to create
> GR> links both on XP and Win7 and it worked fine for both files and
> GR> directories.
> 
> Really. The name “junction.exe” is taletelling: it creates NTFS junction 
> points, not symbolic links for directories. In contrast to junction 
points, 
> by default only Administrators can create symbolic links. You can easily 
> check it in the local security policies.
> 
> b2 tries to create symbolic links by running mklink /D, that is why
> I suggested to change /D to /J, which would tell mklink to create 
> junction points, which 
> in turn doesn't require special privileges.

Ok. What prevents us from changing bjam to always use hardlinks for 
directories?

Gennadiy