Re: [Boost-bugs] [Boost C++ Libraries] #9051: jam build system refuses to work on windows, won't build on mingw-w64

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9051: jam build system refuses to work on windows, won't build on mingw-w64
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-04-04 19:33:14

#9051: jam build system refuses to work on windows, won't build on mingw-w64
-------------------------------+----------------------------
  Reporter:  jmichae3@…        |      Owner:
      Type:  Bugs              |     Status:  new
 Milestone:  To Be Determined  |  Component:  Building Boost
   Version:  Boost 1.54.0      |   Severity:  Showstopper
Resolution:                    |   Keywords:
-------------------------------+----------------------------

Comment (by anonymous):

 the differences between cmd and .bat are larger than just that small
 bullet list. BIG difference. the cmd shell is pretty much a shell
 scripting language.
 when a .bat is used, that functionality is lost - long filenames, long
 paths, etc.
 one issue that may come up is the long filepaths made by the boost
 directories. they are very deep and max out NTFS's filepath limit of 260
 chars (fine for *nix which doesn't have a limit that I know of). also,
 .bat has a commandline limit of 127 chars.
 you should know these limitations before using .bat and program
 accordingly.
 there are workarounds for some of this, like shortened filenames.
 do a for /? to get help.
 for /f has a version of its variable expansion stuff which shortens
 filepaths to 8.3, but know that your compiled result will probably look
 the same and may not be compatible with whoever uses the headers.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/9051#comment:6>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.