[1.34.0] Release Candidate

Hi, The 1.34.0 release candidate is now available from http:// www.boost.org/release/ please give it a try and report any problems to the developer list or directly to me. The tentative release date is May 11. Thanks Thomas -- Thomas Witt witt@acm.org

Hi, I had earlier reported an issue in the built librariy names on win32 using MSVC. I am using VS.net to build boost. The header file (doing an implicit link calling #pragma "link") tries to link to a file with "vc71" but the file has "vc". It is trivial to fix this by editing the "config/auto_link.h" but the proble is in the build generating the wrong file names (wrong: based on the 1_33_1 version of boost and 1_32 version too). IMHO, build on win32 using VS.net needs to get fixed before a final release or each user will start modifying either the header to look for "vc" or modify the build to generate "vc71" or do a manual renaming of files to "vc71" (which I have done). with best regards, dhruva On 5/9/07, Thomas Witt <witt@acm.org> wrote:
Hi,
The 1.34.0 release candidate is now available from http:// www.boost.org/release/ please give it a try and report any problems to the developer list or directly to me.
The tentative release date is May 11.
Thanks
Thomas
-- Thomas Witt witt@acm.org
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Dhruva Krishnamurthy Contents reflect my personal views only!

Just in case you're wondering this post was not meant to be empty. As mentioned earlier the answer is in http://www.boost.org/more/getting_started.html#Tools Autodetect did not make it for 1.34.0 Thomas Thomas Witt wrote:
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Thomas Witt witt@acm.org

on Thu May 10 2007, Thomas Witt <witt-AT-acm.org> wrote:
Just in case you're wondering this post was not meant to be empty.
As mentioned earlier the answer is in
Thomas, I'm confused. I don't think anything in that table is very relevant to 1.34.0, since we're using BBv2 now.
Autodetect did not make it for 1.34.0
Whoops, really? You mean of version numbers? My documentation change says that autodetection works for gcc and msvc. Was I incorrect? I thought you let Rene check in the fix for msvc. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

Hi Sorry for the confusion. David Abrahams wrote:
on Thu May 10 2007, Thomas Witt <witt-AT-acm.org> wrote:
Just in case you're wondering this post was not meant to be empty.
As mentioned earlier the answer is in
Thomas, I'm confused. I don't think anything in that table is very relevant to 1.34.0, since we're using BBv2 now.
It's me being confused. I meant more/getting_started/windows.html and thats in the RC not on the website.
Autodetect did not make it for 1.34.0
Whoops, really? You mean of version numbers? My documentation change says that autodetection works for gcc and msvc. Was I incorrect? I thought you let Rene check in the fix for msvc.
This was a communication error. As of RC2 version numbers for msvc are not auto detected. This will be fixed in RC3. Thanks Thomas -- Thomas Witt witt@acm.org

The new getting started guide is nice, but there are a few things that could be improved. In section 5.2.4 Invoke bjam "--toolset=msvc" is used in the example but with auto-linking not working with auto-detecting toolset using it in a guide aimed at new and inexperienced users. I think it would be better to use "--toolset=msvc-8.0" and users who are not running vc2005 can easily substitute "-8.0" with their version. In the same example "stage" is used but never thoroughly explained and loosely hinted that it is only the name of a directory and that you could use any name A better explanation would be something like this: "The last argument to bjam in this example "stage" represent the type of install you will make, the available options is… (Insert options and explanations)" The link "Boost.Build reference manual" in section 7 is missing index.html and points directly to the directory. On 5/9/07, Thomas Witt <witt@acm.org> wrote:
Hi,
The 1.34.0 release candidate is now available from http:// www.boost.org/release/ please give it a try and report any problems to the developer list or directly to me.
The tentative release date is May 11.
Thanks
Thomas
-- Thomas Witt witt@acm.org
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Galileo wrote:
The new getting started guide is nice, but there are a few things that could be improved.
In section 5.2.4 Invoke bjam "--toolset=msvc" is used in the example but with auto-linking not working with auto-detecting toolset using it in a guide aimed at new and inexperienced users. I think it would be better to use "--toolset=msvc-8.0" and users who are not running vc2005 can easily substitute "-8.0" with their version.
This is intended to work in RC3
In the same example "stage" is used but never thoroughly explained and loosely hinted that it is only the name of a directory and that you could use any name A better explanation would be something like this: "The last argument to bjam in this example "stage" represent the type of install you will make, the available options is… (Insert options and explanations)"
Thanks, I don't think this needs to be fixed for release, but we should not drop it either.
The link "Boost.Build reference manual" in section 7 is missing index.html and points directly to the directory.
Dave? Thomas -- Thomas Witt witt@acm.org
participants (4)
-
David Abrahams
-
dhruva
-
Galileo
-
Thomas Witt