Re: [Boost-bugs] [Boost C++ Libraries] #1720: Need for 32- and 64-bit libraries on Windows with suitable naming convention.

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1720: Need for 32- and 64-bit libraries on Windows with suitable naming convention.
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-03-27 14:27:20


#1720: Need for 32- and 64-bit libraries on Windows with suitable naming
convention.
-----------------------------------+----------------------------------------
  Reporter: snuchia_at_[hidden] | Owner: vladimir_prus
      Type: Feature Requests | Status: new
 Milestone: Boost 1.36.0 | Component: build
   Version: Boost 1.34.1 | Severity: Not Applicable
Resolution: | Keywords: MSVC x64
-----------------------------------+----------------------------------------
Comment (by Steve Nuchia):

 Starting from the index.html in the 1.35.0 RC2 snapshot contained in
 boost-windows-2008-03-24.zip, I can't find the documentation you're
 referring to. Following the instructions in
 more\getting_started\windows.html I find no mention of cross-compilation
 considerations in general nor this very common special case.

 So, it seems to me that there should be a more visible / discoverable link
 to the documentation that does exist; I still don't know where it is. The
 "Boost.Build" documentation I've been able to discover is generic and
 gives no direct help with building boost itself. If you would give me a
 more specific pointer I will draft some new language for the Windows
 getting started guide.

 The suggested change, beyond documentation, is to provide both sets of
 compiled libraries, in the build automation and in the pre-compiled
 installers for Windows, in separate folders named in such a way that they
 can be selected by the Visual Studio defalt platform selection macro: e.g.
 lib-Win32 and lib-x64.

 It doesn't help that the instructions given don't actually work; when I
 run bjam (from boost-jam-3.1.16-1-ntx86.zip) from the root of the boost
 tree I get the error cascade shown below. There has been some traffic on
 the list about bjam compatibility issues and I hope that's all this is.
 The RC2 build-from-source automation is, as it stands and as it is
 documented in the getting started guide, badly broken on Windows. I need
 some help getting past this before I can make good changes to the guide.

 C:\code\Version9\boost>
 C:\code\Version9\boost>bjam --toolset=msvc stage
 notice: could not find main target stage
 notice: assuming it's a name of file to create.
 C:/code/Version9/boost/tools/build/v2/build\project.jam:699: in attribute
 warning: rulename $($(project).attributes).get expands to empty string
 C:/code/Version9/boost/tools/build/v2/build\project.jam:710: in
 project.target
 C:/code/Version9/boost/tools/build/v2\build-system.jam:641: in load
 C:\code\Version9\boost\tools\build\v2/kernel\modules.jam:267: in import
 C:\code\Version9\boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-
 build
 C:\code\Version9\boost\boost-build.jam:11: in module scope
 C:/code/Version9/boost/tools/build/v2/build\project.jam:699: in
 project.attribut
 e
 warning: rulename $($(project).attributes).get expands to empty string
 C:/code/Version9/boost/tools/build/v2/build\targets.jam:202: in
 object(project-t
 arget)@36.__init__
 C:/code/Version9/boost/tools/build/v2/kernel\class.jam:93: in new
 C:/code/Version9/boost/tools/build/v2/build\project.jam:710: in
 project.target
 C:/code/Version9/boost/tools/build/v2\build-system.jam:641: in load
 C:\code\Version9\boost\tools\build\v2/kernel\modules.jam:267: in import
 C:\code\Version9\boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-
 build
 C:\code\Version9\boost\boost-build.jam:11: in module scope
 C:/code/Version9/boost/tools/build/v2/build\project.jam:699: in
 project.attribut
 e
 warning: rulename $($(project).attributes).get expands to empty string
 C:/code/Version9/boost/tools/build/v2/build\targets.jam:221: in get
 C:/code/Version9/boost/tools/build/v2/build\targets.jam:283: in targets-
 to-build

 C:/code/Version9/boost/tools/build/v2/build\targets.jam:252: in
 object(project-t
 arget)@36.generate
 C:/code/Version9/boost/tools/build/v2\build-system.jam:658: in load
 C:\code\Version9\boost\tools\build\v2/kernel\modules.jam:267: in import
 C:\code\Version9\boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-
 build
 C:\code\Version9\boost\boost-build.jam:11: in module scope
 C:/code/Version9/boost/tools/build/v2/build\project.jam:699: in
 project.attribut
 e
 warning: rulename $($(project).attributes).get expands to empty string
 C:/code/Version9/boost/tools/build/v2/build\targets.jam:221: in get
 C:/code/Version9/boost/tools/build/v2/build\targets.jam:284: in targets-
 to-build

 C:/code/Version9/boost/tools/build/v2/build\targets.jam:252: in
 object(project-t
 arget)@36.generate
 C:/code/Version9/boost/tools/build/v2\build-system.jam:658: in load
 C:\code\Version9\boost\tools\build\v2/kernel\modules.jam:267: in import
 C:\code\Version9\boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-
 build
 C:\code\Version9\boost\boost-build.jam:11: in module scope
 don't know how to make <e>stage
 ...found 1 target...
 ...can't find 1 target...

 C:\code\Version9\boost>

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


This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:57 UTC