Re: [boost] b2 headers is unreliable on 1.56 on Windows
Nial,
I found you need to run your cmd prompt as administrator before running b2
in order for the sym links to work correctly, otherwise you end up with
hard links and the process fails 9 times out of 10. At least that is what
I found on Win 8.1,
-Matt
From: Niall Douglas
On 30 Jul 2014 at 20:33, Matthew Musto wrote:
I found you need to run your cmd prompt as administrator before running b2 in order for the sym links to work correctly, otherwise you end up with hard links and the process fails 9 times out of 10. At least that is what I found on Win 8.1,
This is useful to know, however there is no good reason why it shouldn't work properly to begin with. My Jenkins CI slave for Windows does a complete hard link copy of Boost one per test job. Whilst treacle slow compared to Linux, it works perfectly and saves enormous amounts of disc space. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Nial, I found you need to run your cmd prompt as administrator before running b2 in order for the sym links to work correctly, otherwise you end up with hard links and the process fails 9 times out of 10. At least that is what I found on Win 8.1, -Matt
From: Niall Douglas
Subject: b2 headers is unreliable on 1.56 on Windows Newsgroups: gmane.comp.lib.boost.devel Date: 2014-07-30 15:49:37 GMT (8 hours and 40 minutes ago) Anyone else found that b2 headers in 1.56 randomly misses things to hard link on Windows? If you run it four or five times it eventually hard links everything through monte-carlo, but it is a bit annoying.
Niall
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
participants (2)
-
Matthew Musto -
Niall Douglas