[Boost-bugs] [Boost C++ Libraries] #13557: Boost 1.67.0 chrono library Windows build installs NTFS junction

Subject: [Boost-bugs] [Boost C++ Libraries] #13557: Boost 1.67.0 chrono library Windows build installs NTFS junction
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2018-05-01 19:14:37

#13557: Boost 1.67.0 chrono library Windows build installs NTFS junction
------------------------------+---------------------
 Reporter:  george@…          |      Owner:  viboes
     Type:  Bugs              |     Status:  new
Milestone:  To Be Determined  |  Component:  chrono
  Version:  Boost 1.67.0      |   Severity:  Problem
 Keywords:  windows install   |
------------------------------+---------------------
 While testing our internal build of Boost with the latest version, I
 noticed the following problem when building on Windows using MSVC 2015:

 During the build the following statements are logged:

 {{{
 mklink-or-dir boost\chrono\stopwatches

       mklink /J "boost\chrono\stopwatches"
 "libs\chrono\stopwatches\include\boost\chrono\stopwatches"

   Junction created for boost\chrono\stopwatches <<===>>
 libs\chrono\stopwatches\include\boost\chrono\stopwatches
 }}}

 This command creates an NTFS junction, which is something new compared to
 any previous version of Boost I've used (which goes back to 1.50.0).

 My problem is that we're building Boost using our own CMake scripts and
 the CMake "install" command cannot handle NTFS junctions, it simply fails
 during our custom follow-up step that packages the built binaries and
 headers.

 I haven't seen NTFS junctions seen used before, so I wonder if this
 procedure was intentional or not. Is there an option to have the bjam
 install phase make a copy of those files instead of creating the junction?

-- 
Ticket URL: <https://svn.boost.org/trac10/ticket/13557>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.