Full MS compiler version info?
Installation of the final 8.0 (after beta 1 and 2) has caused me some confusion because the output build logs don't contain the full compiler version. For example using a post build event with the test suite, as recommended (- strongly see PS below) --build_info=yes includes this info: Platform: Win32 Compiler: Microsoft Visual C++ version 8.0 STL : Dinkumware standard library version 405 Boost : 1.33.0 The macro _MSC_FULL_VER is 140050215 looks like version 1400 build 50215 Would it be useful to decode in boost/config/compiler/visual.hpp this into version 8.0 and build 50215? (Or?) A new macro BOOST_COMPILER_BUILD ? So that various releases can be distingushed? Paul PS The post CMD.EXE was started with '\\hetp3\i$\boost_1_33_0\libs\test\build\msvc71_proj' as the current directory path. UNC paths are not supported. Defaulting to Windows directory. Running 5 test cases... Which misses showing the full log report that IS shown with an autorun (which is any case much more convenient and recommended by Gennadiy at /boost_1_33_0/libs/test/doc/usage/msvc_net.html etc I found a MS article http://support.microsoft.com/?kbid=156276 about the message '<UNC path>' is an invalid current directory path. UNC paths are not supported. Defaulting to Windows directory. The article does not seem accurate and I have queried it with MS. I have also previously seen with the logging library (proposed). -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com www.hetp.u-net.com
Paul A Bristow wrote:
Installation of the final 8.0 (after beta 1 and 2) has caused me some confusion because the output build logs don't contain the full compiler version. For example using a post build event with the test suite, as recommended (- strongly see PS below)
--build_info=yes
includes this info:
Platform: Win32 Compiler: Microsoft Visual C++ version 8.0 STL : Dinkumware standard library version 405 Boost : 1.33.0
The macro _MSC_FULL_VER is 140050215
looks like version 1400 build 50215
Would it be useful to decode in boost/config/compiler/visual.hpp this into version 8.0 and build 50215? (Or?)
A new macro BOOST_COMPILER_BUILD ?
So that various releases can be distingushed?
You mean like this: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostConfig BOOST_USER: BoostConfig -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Indeed - but I didn't see the MS BUILD number - needed to distinguish between 8.0 beta 1, 2, 2.5 ... and final(s). Microsoft have ideas on version numbering which seem dotty to me, but they have ... Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com www.hetp.u-net.com | -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Rene Rivera | Sent: 23 November 2005 19:25 | To: boost@lists.boost.org | Subject: Re: [boost] Full MS compiler version info? | | Paul A Bristow wrote: | > Installation of the final 8.0 (after beta 1 and 2) has | caused me some | > confusion because the output build logs don't contain the | full compiler | > version. For example using a post build event with the | test suite, as | > recommended (- strongly see PS below) | > | > --build_info=yes | > | > includes this info: | > | > Platform: Win32 | > Compiler: Microsoft Visual C++ version 8.0 | > STL : Dinkumware standard library version 405 | > Boost : 1.33.0 | > | > The macro _MSC_FULL_VER is 140050215 | > | > looks like version 1400 build 50215 | > | > Would it be useful to decode in | boost/config/compiler/visual.hpp this into | > version 8.0 and build 50215? (Or?) | > | > A new macro BOOST_COMPILER_BUILD ? | > | > So that various releases can be distingushed? | | You mean like this: | | http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl | ?BoostConfig | BOOST_USER: BoostConfig | |
| -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov | Sent: 24 November 2005 12:46 | To: boost@lists.boost.org | Subject: Re: [boost] Full MS compiler version info? | | Paul A Bristow wrote: | | > Indeed - but I didn't see the MS BUILD number - needed to | distinguish | > between 8.0 beta 1, 2, 2.5 ... and final(s). | | Why is it needed? Beta versions don't exist as far as | official support is concerned. Of course, but I am sure I am not alone in wanting to anticipate problems and improvements in testing new versions before the release. Indeed this is how Boost gives 'official' support to new versions as quickly as it does? It may be too, that there is more than one release of "8.0". The build number gives assurance that this is NOT a cause of mysterious differences. Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com www.hetp.u-net.com
Paul A Bristow wrote:
Indeed - but I didn't see the MS BUILD number - needed to distinguish between 8.0 beta 1, 2, 2.5 ... and final(s). Microsoft have ideas on version numbering which seem dotty to me, but they have ...
There's a comment about the number of digits for each part of the version number: "Some more thinking on the version number... I think it's relatively safe to set it at 2/2/5. That covers MSVC which has the large patch numbers. And covers CW, and others, which are up to and past 10 for the major number." The intent, as it's not explicit since the MSVC define is not there yet, is that the patch number for MSVC will be the build number. So in your previous example the version would be 8.0.50215. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
| -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Rene Rivera | Sent: 24 November 2005 16:06 | To: boost@lists.boost.org | Subject: Re: [boost] Full MS compiler version info? | | Paul A Bristow wrote: | > Indeed - but I didn't see the MS BUILD number - needed to | distinguish | > between 8.0 beta 1, 2, 2.5 ... and final(s). Microsoft | have ideas on | > version numbering which seem dotty to me, but they have ... | | There's a comment about the number of digits for each part of the | version number: "Some more thinking on the version number... I think | it's relatively safe to set it at 2/2/5. That covers MSVC | which has the | large patch numbers. And covers CW, and others, which are up | to and past | 10 for the major number." The intent, as it's not explicit since the | MSVC define is not there yet, is that the patch number for | MSVC will be | the build number. So in your previous example the version would be | 8.0.50215. This sounds just the job! (until the build counter gets to 100000!) Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com www.hetp.u-net.com
"Paul A Bristow" <pbristow@hetp.u-net.com> wrote in message news:E1Eeyor-00040R-NP@he303war.uk.vianw.net...
PS
The post
CMD.EXE was started with '\\hetp3\i$\boost_1_33_0\libs\test\build\msvc71_proj' as the current directory path. UNC paths are not supported. Defaulting to Windows directory.
Two leading backslashes cause the path to be interpreted as a UNC path rather than a file system path. The fix is to use a single backslash. --Beman
Well that sounds very plausible, but I am puzzled as to where I should alter this. I have installed the Boost library in the usual way and chosen the solution by opening it from File Open solution The Path of the solution is shown in the Properties page below \\Hetp3\i$\boost_1_33_0\libs\test\build\msvc71_proj\boost_test_library.sln but is greyed out so I can't alter it. I am building and running unit_test_example1 project. The project property page shows .\Debug/unit_test_example1.exe as the output file. It is set as the startup project and I press ctrl F5 So where/how can I alter the descriptor to use a single backslash? (Or just remove the computer name from the path?) Thanks Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com www.hetp.u-net.com | -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes | Sent: 26 November 2005 22:06 | To: boost@lists.boost.org | Subject: Re: [boost] Full MS compiler version info? | | > | > CMD.EXE was started with | > '\\hetp3\i$\boost_1_33_0\libs\test\build\msvc71_proj' as the current | > directory path. UNC paths | > are not supported. Defaulting to Windows directory. | | Two leading backslashes cause the path to be interpreted as a | UNC path rather than a file system path. The fix is to use a single backslash.
participants (4)
-
Beman Dawes -
Paul A Bristow -
Peter Dimov -
Rene Rivera