Quantcast

[release] 1.64.0 please test master snapshot..

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
35 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
After help from various sources to get the VS2017 building working the
latest master snapshot should at least try and build with VS2017. Assuming
nothing horrible shows up today we will release the first beta tonight.
Hence, please smoke test the latest master snapshot found at:

<https://dl.bintray.com/boostorg/master/>

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On 16 March 2017 at 13:09, Rene Rivera via Boost <[hidden email]> wrote:
> After help from various sources to get the VS2017 building working the
> latest master snapshot should at least try and build with VS2017. Assuming
> nothing horrible shows up today we will release the first beta tonight.
> Hence, please smoke test the latest master snapshot found at:
>
> <https://dl.bintray.com/boostorg/master/>

Thanks for the snapshot.

I did quick building subset of libraries using VS2017,
with ZLIB_SOURCE and BZIP2_SOURCE defined.
The build was successful. I did not run any tests though.
Brief configuration log copied below.

Kudos to Tom Kent for recent patches towards VS2017 support.

Minor issue:
- I run build inside "x64 Native Tools Command Prompt for VS 2017"
- That is, using native 64-bit CL.EXE and targetting 64-bit platform.
- In config.log, I see b2_msvc_14.10.25017_vcvarsx86_amd64_.cmd
- In processes, I see b2 runs CL.EXE 32-bit cross-compiuler targetting 64-bit
Would it be possible to run CL.exe 64-bit binary?
Given I'm in the VS2017 command prompt configured with native 64-bit toolset...

Regards,
Mateusz

###################################################
Building Boost.Build engine

Bootstrapping is done. To build, run:

    .\b2

To adjust configuration, edit 'project-config.jam'.
Further information:

    - Command line help:
    .\b2 --help

    - Getting started guide:
    http://boost.org/more/getting_started/windows.html

    - Boost.Build documentation:
    http://www.boost.org/build/doc/html/index.html
Performing configuration checks

    - 32-bit                   : yes
    - arm                      : no
    - mips1                    : no
    - power                    : no
    - sparc                    : no
    - x86                      : yes

Building the Boost C++ Libraries.


    - symlinks supported       : no
    - junctions supported      : yes
    - hardlinks supported      : yes
    - has_icu builds           : no

Component configuration:

    - atomic                   : not building
    - chrono                   : building
    - container                : not building
    - context                  : not building
    - coroutine                : not building
    - coroutine2               : not building
    - date_time                : building
    - exception                : not building
    - fiber                    : not building
    - filesystem               : building
    - graph                    : not building
    - graph_parallel           : not building
    - iostreams                : building
    - locale                   : not building
    - log                      : not building
    - math                     : not building
    - metaparse                : not building
    - mpi                      : not building
    - program_options          : building
    - python                   : not building
    - random                   : not building
    - regex                    : building
    - serialization            : not building
    - signals                  : not building
    - system                   : building
    - test                     : building
    - thread                   : building
    - timer                    : not building
    - type_erasure             : not building
    - wave                     : not building
###################################################


--
Mateusz Loskot, http://mateusz.loskot.net

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Mar 16, 2017 at 1:09 PM, Rene Rivera via Boost
<[hidden email]> wrote:
> After help from various sources to get the VS2017 building working the
> latest master snapshot should at least try and build with VS2017. Assuming
> nothing horrible shows up today we will release the first beta tonight.
> Hence, please smoke test the latest master snapshot found at:
>
> <https://dl.bintray.com/boostorg/master/>

VS2017 / W7:
...found 37620 targets...

The Boost C++ Libraries were successfully built!

Awesome, thanks a lot!


--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
Rene Rivera wrote:
> After help from various sources to get the VS2017 building working the
> latest master snapshot should at least try and build with VS2017. Assuming
> nothing horrible shows up today we will release the first beta tonight.
> Hence, please smoke test the latest master snapshot found at:
>
> <https://dl.bintray.com/boostorg/master/>

Worked for me using "b2 -j 8 toolset=msvc-14.10".

Appveyor is also fixed. Thanks very much to all responsible!

I do have one issue with the new 14.10 toolset though, unrelated to the
above snapshot. It's that I have, in user-config.jam, the following:

import feature ;
import toolset ;

using msvc : 8.0 ;

feature.subfeature toolset msvc : std : cxx14 cxxlatest : optional composite
propagated ;

feature.compose <toolset-msvc:std>cxx14 : <cxxflags>/std:c++14 ;
feature.compose <toolset-msvc:std>cxxlatest : <cxxflags>/std:c++latest ;

which allows me to use "toolset=msvc-cxxlatest-14.0". But it doesn't work
with 14.10; I get:

C:\Projects\boost-git\boost\libs\mp11>b2 -j 8 test
toolset=msvc-cxxlatest-14.10
C:/Projects/boost-git/boost/tools/build/src/build\feature.jam:313: in
implied-subfeature from module feature
error: "14.10" is not a known subfeature value of <toolset>msvc
C:/Projects/boost-git/boost/tools/build/src/build\feature.jam:500: in
feature.validate-value-string from module feature
C:/Projects/boost-git/boost/tools/build/src/build\property.jam:276: in
validate1 from module property
C:/Projects/boost-git/boost/tools/build/src/build\property.jam:302: in
validatefrom module property
C:/Projects/boost-git/boost/tools/build/src/build\property.jam:311: in
property.validate-property-sets from module property
C:/Projects/boost-git/boost/tools/build/src/build\toolset.jam:156: in
toolset.flags from module toolset
C:/Projects/boost-git/boost/tools/build/src/tools\common.jam:438: in
common.handle-options from module common
C:/Projects/boost-git/boost/tools/build/src/tools\msvc.jam:928: in
configure-really from module msvc
C:/Projects/boost-git/boost/tools/build/src/tools\msvc.jam:201: in configure
from module msvc
C:/Projects/boost-git/boost/tools/build/src/tools\msvc.jam:153: in msvc.init
from module msvc
C:/Projects/boost-git/boost/tools/build/src/build\toolset.jam:43: in
toolset.using from module toolset
C:/Projects/boost-git/boost/tools/build/src\build-system.jam:461: in
process-explicit-toolset-requests from module build-system
C:/Projects/boost-git/boost/tools/build/src\build-system.jam:527: in load
from module build-system
C:\Projects\boost-git\boost\tools\build\src/kernel\modules.jam:295: in
import from module modules
C:\Projects\boost-git\boost\tools\build\src/kernel/bootstrap.jam:139: in
boost-build from module
C:\Projects\boost-git\boost\boost-build.jam:17: in module scope from module

There's probably a place that is missing 14.10 somewhere.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Mar 16, 2017 at 7:09 AM, Rene Rivera via Boost <
[hidden email]> wrote:

> After help from various sources to get the VS2017 building working the
> latest master snapshot should at least try and build with VS2017. Assuming
> nothing horrible shows up today we will release the first beta tonight.
> Hence, please smoke test the latest master snapshot found at:
>
> <https://dl.bintray.com/boostorg/master/>
>

VS2017 is not yet working with master. When building the libraries it
builds in the format "libboost_thread-vc1410-mt-1_64.lib", however the code
in config/auto_link.hpp still has a vc150 in it, meaning any time you try
to link a library you will get an error "libboost_thread-vc150-mt-1_64.lib
not found".

I think that is easy enough to fix (and drastic enough) that we should hold
the beta for it, but I defer to the release team.

Tom

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On Thu, Mar 16, 2017 at 4:00 PM, Tom Kent via Boost <[hidden email]>
wrote:

> On Thu, Mar 16, 2017 at 7:09 AM, Rene Rivera via Boost <
> [hidden email]> wrote:
>
> > After help from various sources to get the VS2017 building working the
> > latest master snapshot should at least try and build with VS2017.
> Assuming
> > nothing horrible shows up today we will release the first beta tonight.
> > Hence, please smoke test the latest master snapshot found at:
> >
> > <https://dl.bintray.com/boostorg/master/>
> >
>
> VS2017 is not yet working with master. When building the libraries it
> builds in the format "libboost_thread-vc1410-mt-1_64.lib", however the
> code
> in config/auto_link.hpp still has a vc150 in it, meaning any time you try
> to link a library you will get an error "libboost_thread-vc150-mt-1_64.lib
> not found".
>
> I think that is easy enough to fix (and drastic enough) that we should hold
> the beta for it, but I defer to the release team.
>

Does master config have the changes for this? Does develop config? What are
the changes?


--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On Thu, Mar 16, 2017 at 5:03 PM, Rene Rivera via Boost <
[hidden email]> wrote:

> On Thu, Mar 16, 2017 at 4:00 PM, Tom Kent via Boost <[hidden email]
> >
> wrote:
>
> > On Thu, Mar 16, 2017 at 7:09 AM, Rene Rivera via Boost <
> > [hidden email]> wrote:
> >
> > > After help from various sources to get the VS2017 building working the
> > > latest master snapshot should at least try and build with VS2017.
> > Assuming
> > > nothing horrible shows up today we will release the first beta tonight.
> > > Hence, please smoke test the latest master snapshot found at:
> > >
> > > <https://dl.bintray.com/boostorg/master/>
> > >
> >
> > VS2017 is not yet working with master. When building the libraries it
> > builds in the format "libboost_thread-vc1410-mt-1_64.lib", however the
> > code
> > in config/auto_link.hpp still has a vc150 in it, meaning any time you try
> > to link a library you will get an error "libboost_thread-vc150-mt-1_
> 64.lib
> > not found".
> >
> > I think that is easy enough to fix (and drastic enough) that we should
> hold
> > the beta for it, but I defer to the release team.
> >
>
> Does master config have the changes for this? Does develop config? What are
> the changes?
>

After a pull on both,
C:\boost\develop\libs\config\include\boost\config\auto_link.hpp  lines
171-172:

     // vc14.1:
#    define BOOST_LIB_TOOLSET "vc141"

but C:\boost\master\libs\config\include\boost\config\auto_link.hpp lines
171-172:

   // vc15:
#  define BOOST_LIB_TOOLSET "vc150"

IIUC, develop is correct, while master is out-of-date.

So it looks like at the least develop for config needs to be merged into
master for config.

HTH,

--Beman

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
Beman Dawes wrote:
...
> > > VS2017 is not yet working with master. When building the libraries it
> > > builds in the format "libboost_thread-vc1410-mt-1_64.lib", ...

> After a pull on both,
> C:\boost\develop\libs\config\include\boost\config\auto_link.hpp  lines
> 171-172:
>
>      // vc14.1:
> #    define BOOST_LIB_TOOLSET "vc141"
>
> but C:\boost\master\libs\config\include\boost\config\auto_link.hpp lines
> 171-172:
>
>    // vc15:
> #  define BOOST_LIB_TOOLSET "vc150"
>
> IIUC, develop is correct, while master is out-of-date.

Looks like neither is correct; should be "vc1410".


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On Thu, Mar 16, 2017 at 4:59 PM, Peter Dimov via Boost <
[hidden email]> wrote:

> Beman Dawes wrote:
> ...
>
>> > > VS2017 is not yet working with master. When building the libraries it
>> > > builds in the format "libboost_thread-vc1410-mt-1_64.lib", ...
>>
>
> After a pull on both,
>> C:\boost\develop\libs\config\include\boost\config\auto_link.hpp  lines
>> 171-172:
>>
>>      // vc14.1:
>> #    define BOOST_LIB_TOOLSET "vc141"
>>
>> but C:\boost\master\libs\config\include\boost\config\auto_link.hpp lines
>> 171-172:
>>
>>    // vc15:
>> #  define BOOST_LIB_TOOLSET "vc150"
>>
>> IIUC, develop is correct, while master is out-of-date.
>>
>
> Looks like neither is correct; should be "vc1410".


I submitted a pull request against develop to change to this, which matches
the library output.

Tom

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On 17/03/2017 12:59, Tom Kent via Boost wrote:
>> Looks like neither is correct; should be "vc1410".
>
> I submitted a pull request against develop to change to this, which matches
> the library output.

I asked this in another thread (I don't have a VS2017 install locally to
check): what does $(PlatformToolsetVersion) in VS2017 C++ projects
evaluate to?

Because if that number is different than what Boost is putting in the
filenames, it's going to cause integration pain to someone.



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
On Thu, Mar 16, 2017 at 7:36 PM, Gavin Lambert via Boost <
[hidden email]> wrote:

> On 17/03/2017 12:59, Tom Kent via Boost wrote:
>
>> Looks like neither is correct; should be "vc1410".
>>>
>>
>> I submitted a pull request against develop to change to this, which
>> matches
>> the library output.
>>
>
> I asked this in another thread (I don't have a VS2017 install locally to
> check): what does $(PlatformToolsetVersion) in VS2017 C++ projects evaluate
> to?
>
> Because if that number is different than what Boost is putting in the
> filenames, it's going to cause integration pain to someone.


 $(PlatformToolsetVersion) is "141".

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Mar 16, 2017 at 9:36 AM, Mateusz Loskot via Boost <
[hidden email]> wrote:

> On 16 March 2017 at 13:09, Rene Rivera via Boost <[hidden email]>
> wrote:
> > After help from various sources to get the VS2017 building working the
> > latest master snapshot should at least try and build with VS2017.
> Assuming
> > nothing horrible shows up today we will release the first beta tonight.
> > Hence, please smoke test the latest master snapshot found at:
> >
> > <https://dl.bintray.com/boostorg/master/>
>
> Thanks for the snapshot.
>
> I did quick building subset of libraries using VS2017,
> with ZLIB_SOURCE and BZIP2_SOURCE defined.
> The build was successful. I did not run any tests though.
> Brief configuration log copied below.
>
> Kudos to Tom Kent for recent patches towards VS2017 support.
>
> Minor issue:
> - I run build inside "x64 Native Tools Command Prompt for VS 2017"
> - That is, using native 64-bit CL.EXE and targetting 64-bit platform.
> - In config.log, I see b2_msvc_14.10.25017_vcvarsx86_amd64_.cmd
> - In processes, I see b2 runs CL.EXE 32-bit cross-compiuler targetting
> 64-bit
> Would it be possible to run CL.exe 64-bit binary?
> Given I'm in the VS2017 command prompt configured with native 64-bit
> toolset...
>

I think this comes from build/src/tools/msvc.jam:1055. I'm not sure what to
do about it though. I guess we need to look at the env variables:
PROCESSOR_ARCHITECTURE, Platform, and PreferredToolArchitecture.

I did a quick check running all five command windows on two VMs, one
running a 64-bit win2012R2 and one running a 32-bit win7.

On 64-bit windows install

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio
2017\Visual Studio Tools

Developer Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat"
Sets: PROCESSOR_ARCHITECTURE=AMD64

x64 Native Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat"
Sets: Platform=x64 PROCESSOR_ARCHITECTURE=AMD64

x64_x86 Cross Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsamd64_x86.bat"
Sets: Platform=x86 PreferredToolArchitecture=x64
PROCESSOR_ARCHITECTURE=AMD64

x86 Native Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars32.bat"
Sets: Platform=x86 PROCESSOR_ARCHITECTURE=AMD64

x86_x64 Cross Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files (x86)\Microsoft Visual
Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsx86_amd64.bat"
Sets: Platform=x64 PROCESSOR_ARCHITECTURE=AMD64


On Windows 7 - 32 Bit Install

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio
2017\Visual Studio Tools

Developer Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files\Microsoft Visual
Studio\2017\Community\Common7\Tools\VsDevCmd.bat"
Sets:  PROCESSOR_ARCHITECTURE=x86

x64 Native Tools Command Prompt for VS 2017  (cl.exe doesn't run!)
Runs: %comspec% /k "C:\Program Files\Microsoft Visual
Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat"
Sets: Platform=x64 PROCESSOR_ARCHITECTURE=x86

x64_x86 Cross Tools Command Prompt for VS 2017 (cl.exe doesn't run!)
Runs: %comspec% /k "C:\Program Files\Microsoft Visual
Studio\2017\Community\VC\Auxiliary\Build\vcvarsamd64_x86.bat"
Sets: Platform=x86 PreferredToolArchitecture=x64 PROCESSOR_ARCHITECTURE=x86

x86 Native Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files\Microsoft Visual
Studio\2017\Community\VC\Auxiliary\Build\vcvars32.bat"
Sets: Platform=x86 PROCESSOR_ARCHITECTURE=x86

x86_x64 Cross Tools Command Prompt for VS 2017
Runs: %comspec% /k "C:\Program Files\Microsoft Visual
Studio\2017\Community\VC\Auxiliary\Build\vcvarsx86_amd64.bat"
Sets: Platform=x64 PROCESSOR_ARCHITECTURE=x86


The full output of the DOS "set" command for each shell is in this gist:
https://gist.github.com/teeks99/627dce6f298ba02592643f03fe36a68b

Tom

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 17/03/2017 13:47, Tom Kent via Boost wrote:

> On Thu, Mar 16, 2017 at 7:36 PM, Gavin Lambert via Boost <
> [hidden email]> wrote:
>
>> On 17/03/2017 12:59, Tom Kent via Boost wrote:
>>
>>> Looks like neither is correct; should be "vc1410".
>>>>
>>>
>>> I submitted a pull request against develop to change to this, which
>>> matches
>>> the library output.
>>>
>>
>> I asked this in another thread (I don't have a VS2017 install locally to
>> check): what does $(PlatformToolsetVersion) in VS2017 C++ projects evaluate
>> to?
>>
>> Because if that number is different than what Boost is putting in the
>> filenames, it's going to cause integration pain to someone.
>
>
>  $(PlatformToolsetVersion) is "141".

So then shouldn't b2 and Config be using "*-vc141-*"?



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Mar 16, 2017 at 7:47 PM, Tom Kent via Boost <[hidden email]>
wrote:

> On Thu, Mar 16, 2017 at 7:36 PM, Gavin Lambert via Boost <
> [hidden email]> wrote:
>
> > On 17/03/2017 12:59, Tom Kent via Boost wrote:
> >
> >> Looks like neither is correct; should be "vc1410".
> >>>
> >>
> >> I submitted a pull request against develop to change to this, which
> >> matches
> >> the library output.
> >>
> >
> > I asked this in another thread (I don't have a VS2017 install locally to
> > check): what does $(PlatformToolsetVersion) in VS2017 C++ projects
> evaluate
> > to?
> >
> > Because if that number is different than what Boost is putting in the
> > filenames, it's going to cause integration pain to someone.
>
>
>  $(PlatformToolsetVersion) is "141".
>

Personally I would prefer 14.10 (aka 1410) because of purely selfish
reasons. As it would mean Boost Predef already says that "14.10" is the
version. But otherwise I don't care what version number it is. I'm beyond
exhausted from dealing with VS version numbers. Which means..

1. For the beta the version is "14.10", aka "1410".
2. And we'll apply the Boost Config patch accordingly.
3. After beta everyone can fight over what the "real" version number should
be.
4. Apply changes after enough people agree. And if that's fast enough.. We
can do another beta. Other we just wait for the release to have the change.

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Thu, Mar 16, 2017 at 6:59 PM, Tom Kent via Boost <[hidden email]>
wrote:

> On Thu, Mar 16, 2017 at 4:59 PM, Peter Dimov via Boost <
> [hidden email]> wrote:
>
> > Beman Dawes wrote:
> > ...
> >
> >> > > VS2017 is not yet working with master. When building the libraries
> it
> >> > > builds in the format "libboost_thread-vc1410-mt-1_64.lib", ...
> >>
> >
> > After a pull on both,
> >> C:\boost\develop\libs\config\include\boost\config\auto_link.hpp  lines
> >> 171-172:
> >>
> >>      // vc14.1:
> >> #    define BOOST_LIB_TOOLSET "vc141"
> >>
> >> but C:\boost\master\libs\config\include\boost\config\auto_link.hpp
> lines
> >> 171-172:
> >>
> >>    // vc15:
> >> #  define BOOST_LIB_TOOLSET "vc150"
> >>
> >> IIUC, develop is correct, while master is out-of-date.
> >>
> >
> > Looks like neither is correct; should be "vc1410".
>
>
> I submitted a pull request against develop to change to this, which matches
> the library output.
>

I can't seem to cherry-pick it to master.

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Fri, Mar 17, 2017 at 3:05 AM, Rene Rivera via Boost
<[hidden email]> wrote:

>>  $(PlatformToolsetVersion) is "141".
>>
>
> Personally I would prefer 14.10 (aka 1410) because of purely selfish
> reasons. As it would mean Boost Predef already says that "14.10" is the
> version. But otherwise I don't care what version number it is. I'm beyond
> exhausted from dealing with VS version numbers. Which means..
>
> 1. For the beta the version is "14.10", aka "1410".
> 2. And we'll apply the Boost Config patch accordingly.
> 3. After beta everyone can fight over what the "real" version number should
> be.
> 4. Apply changes after enough people agree. And if that's fast enough.. We
> can do another beta. Other we just wait for the release to have the change.

Where is 14.10 coming from?
In the IDE and vcxproj files I only see 141.


--
Olaf

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list

>> Personally I would prefer 14.10 (aka 1410) because of purely selfish
>> reasons. As it would mean Boost Predef already says that "14.10" is the
>> version. But otherwise I don't care what version number it is. I'm beyond
>> exhausted from dealing with VS version numbers. Which means..
>>
>> 1. For the beta the version is "14.10", aka "1410".
>> 2. And we'll apply the Boost Config patch accordingly.
>> 3. After beta everyone can fight over what the "real" version number should
>> be.
>> 4. Apply changes after enough people agree. And if that's fast enough.. We
>> can do another beta. Other we just wait for the release to have the change.
> Where is 14.10 coming from?
> In the IDE and vcxproj files I only see 141.

Nod.

I asked about this on the PR and got no reply, so let's try again here...

We have history here - of using 3 figure version names, that includes
VC7.1 which had the "71" suffix, IMO the trailing zero is at best
superfluous, and at worst confusing.  We should be consistent both with
what we've done before, and with what MSVC reports.

There is another issue with Boost.Build:

* Open up a Visual studio 2017 command prompt, and bootstrap, then:
* ./b2 toolset=msvc-14.10 builds libraries with the "1410" suffix, but:
* ./b2 toolset=msvc-14.1 also seems to work and builds libraries with a
"141" suffix.

That shouldn't happen!

Best, John.

---
This email has been checked for viruses by AVG.
http://www.avg.com


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Marcel Raad
In reply to this post by Boost - Dev mailing list
Boost - Dev mailing list wrote
On 17/03/2017 13:47, Tom Kent via Boost wrote:
> On Thu, Mar 16, 2017 at 7:36 PM, Gavin Lambert via Boost <
> [hidden email]> wrote:
>
>>
>> I asked this in another thread (I don't have a VS2017 install locally to
>> check): what does $(PlatformToolsetVersion) in VS2017 C++ projects evaluate
>> to?
>>
>> Because if that number is different than what Boost is putting in the
>> filenames, it's going to cause integration pain to someone.
>
>
>  $(PlatformToolsetVersion) is "141".

So then shouldn't b2 and Config be using "*-vc141-*"?
+1, I would also expect it to match $(PlatformToolsetVersion).

Apart from that, everything works for me except the 150/1410 mismatch for autolinking that has already been mentioned. Thanks for bringing VS2017 support to Boost 1.64 at the last minute to all involved!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 17 March 2017 at 02:08, Tom Kent via Boost <[hidden email]> wrote:

> On Thu, Mar 16, 2017 at 9:36 AM, Mateusz Loskot via Boost <
> [hidden email]> wrote:
>
>> On 16 March 2017 at 13:09, Rene Rivera via Boost <[hidden email]>
>> wrote:
>> > After help from various sources to get the VS2017 building working the
>> > latest master snapshot should at least try and build with VS2017.
>> Assuming
>> > nothing horrible shows up today we will release the first beta tonight.
>> > Hence, please smoke test the latest master snapshot found at:
>> >
>> > <https://dl.bintray.com/boostorg/master/>
>>
>> Thanks for the snapshot.
>>
>> I did quick building subset of libraries using VS2017,
>> with ZLIB_SOURCE and BZIP2_SOURCE defined.
>> The build was successful. I did not run any tests though.
>> Brief configuration log copied below.
>>
>> Kudos to Tom Kent for recent patches towards VS2017 support.
>>
>> Minor issue:
>> - I run build inside "x64 Native Tools Command Prompt for VS 2017"
>> - That is, using native 64-bit CL.EXE and targetting 64-bit platform.
>> - In config.log, I see b2_msvc_14.10.25017_vcvarsx86_amd64_.cmd
>> - In processes, I see b2 runs CL.EXE 32-bit cross-compiuler targetting
>> 64-bit
>> Would it be possible to run CL.exe 64-bit binary?
>> Given I'm in the VS2017 command prompt configured with native 64-bit
>> toolset...
>
>
> I think this comes from build/src/tools/msvc.jam:1055. I'm not sure what to
> do about it though. I guess we need to look at the env variables:
> PROCESSOR_ARCHITECTURE, Platform, and PreferredToolArchitecture.

PreferredToolArchitecture as the hint would also be consistent with MSBuild.

I've tried to force b2 to use 64-bit binary of cl.exe.
I added this to project-config.jam

using msvc
    : 14.10
    : "C:\\Program Files (x86)\\Microsoft Visual
Studio\\2017\\Professional\\VC\\Tools\\MSVC\\14.10.25017\\bin\\HostX64\\x64\\cl.exe"
    ;

But then, it looks like failing to recognise the toolset:

b2 toolset=msvc-14.10


F:/boost/tools/build/src/tools\msvc.jam:1103: in configure-really
*** argument error
* rule generate-setup-cmd ( version : command : parent : options * :
cpu : global-setup ? : default-global-setup-options : default-setup )
* called with: ( 14.10.25017 14.10.25017 : C:\Program Files
(x86)\Microsoft Visual
Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64 :
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64 :
<command>C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\cl.exe
<command>C:\Program Files (x86)\Microsoft Visual
Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe
: i386 :  : x86 : vcvars32.bat )
* extra argument 14.10.25017
F:/boost/tools/build/src/tools\msvc.jam:811:see definition of rule
'generate-setup-cmd' being called
F:/boost/tools/build/src/tools\msvc.jam:201: in configure
F:/boost/tools/build/src/tools\msvc.jam:153: in msvc.init
F:/boost/tools/build/src/build\toolset.jam:43: in toolset.using
F:/boost/tools/build/src/build\project.jam:1052: in using
project-config.jam:6: in modules.load
F:/boost/tools/build/src\build-system.jam:249: in load-config
F:/boost/tools/build/src\build-system.jam:412: in load-configuration-files
F:/boost/tools/build/src\build-system.jam:524: in load
F:\boost\tools\build\src/kernel\modules.jam:295: in import
F:\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build
F:\boost\boost-build.jam:17: in module scope
F:\boost>




Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [release] 1.64.0 please test master snapshot..

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On 17 March 2017 at 10:00, John Maddock via Boost <[hidden email]> wrote:

>
>>> Personally I would prefer 14.10 (aka 1410) because of purely selfish
>>> reasons. As it would mean Boost Predef already says that "14.10" is the
>>> version. But otherwise I don't care what version number it is. I'm beyond
>>> exhausted from dealing with VS version numbers. Which means..
>>>
>>> 1. For the beta the version is "14.10", aka "1410".
>>> 2. And we'll apply the Boost Config patch accordingly.
>>> 3. After beta everyone can fight over what the "real" version number
>>> should
>>> be.
>>> 4. Apply changes after enough people agree. And if that's fast enough..
>>> We
>>> can do another beta. Other we just wait for the release to have the
>>> change.
>>
>> Where is 14.10 coming from?
>> In the IDE and vcxproj files I only see 141.
>
>
> Nod.
>
> I asked about this on the PR and got no reply, so let's try again here...
>
> We have history here - of using 3 figure version names, that includes VC7.1
> which had the "71" suffix, IMO the trailing zero is at best superfluous, and
> at worst confusing.  We should be consistent both with what we've done
> before, and with what MSVC reports.

Speaking of consistency, perhaps these two could be unified
instead of adding up to the forest of names [1]

bootstrap.bat vc1410
b2 toolset=msvc-14.10

[1] http://lists.boost.org/Archives/boost/2017/03/233387.php
--
Mateusz Loskot, http://mateusz.loskot.net

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
12
Loading...