[1.33.0] Release candidate #1 is available
Boost 1.33.0 release candidate #1 is now available here: http://www.osl.iu.edu/~dgregor/boost-1.33.0/ There are two sets of files important for this release: - boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc. Thanks! Doug Gregor 1.33.0 Release Manager
Doug Gregor <dgregor@cs.indiana.edu> writes:
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
And the whole thing can be also browsed online at http://engineering.meta-comm.com/boost/1_33_0_rc1/. -- Aleksey Gurtovoy MetaCommunications Engineering
Hi, I looked at the peoples http://engineering.meta-comm.com/boost/1_33_0_rc1/people/people.htm page. The picture of Jonathan Turkanis is missing. Best regards Johannes "Aleksey Gurtovoy" <agurtovoy@meta-comm.com> schrieb im Newsbeitrag news:m1u0i84mua.fsf@tulip.office.meta...
Doug Gregor <dgregor@cs.indiana.edu> writes:
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
And the whole thing can be also browsed online at http://engineering.meta-comm.com/boost/1_33_0_rc1/.
-- Aleksey Gurtovoy MetaCommunications Engineering _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
people/people.htm says it was revised 21 October 2004, which can't be right since the live version says that and is different.
"Doug Gregor" <dgregor@cs.indiana.edu> wrote in message news:fd51e35e72ebd969092c577d7941d767@cs.indiana.edu...
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
Is it OK to make minor wording tweaks to the home page? -- Fix missing "be" typo and TR2 clarification from Joe Gottman. -- Refine "Getting started" wording to make it clearer Boost works on Windows too. I tried to make these a couple of days ago, but got stopped by CVS being offline. --Beman
I love the new website, but alas I found a very minor validation problem with the xthml : http://validator.w3.org/check?verbose=1&uri=http%3A//engineering.meta-comm.com/boost/1_33_0_rc1/ ( http://tinyurl.com/9dacm ) blockquote can only contain block level elements, so you need a <p> or a <div> surrounding the <span>s See : http://www.w3schools.com/tags/tag_blockquote.asp Sam On 8/2/05, Beman Dawes <bdawes@acm.org> wrote:
"Doug Gregor" <dgregor@cs.indiana.edu> wrote in message news:fd51e35e72ebd969092c577d7941d767@cs.indiana.edu...
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
Is it OK to make minor wording tweaks to the home page?
-- Fix missing "be" typo and TR2 clarification from Joe Gottman. -- Refine "Getting started" wording to make it clearer Boost works on Windows too.
I tried to make these a couple of days ago, but got stopped by CVS being offline.
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Sam Partington wrote:
I love the new website, but alas I found a very minor validation problem with the xthml :
http://validator.w3.org/check?verbose=1&uri=http%3A//engineering.meta-comm.com/boost/1_33_0_rc1/ ( http://tinyurl.com/9dacm )
blockquote can only contain block level elements, so you need a <p> or a <div> surrounding the <span>s
Thanks for finding that. It's fixed now. -- -- 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
On Aug 2, 2005, at 6:56 AM, Beman Dawes wrote:
"Doug Gregor" <dgregor@cs.indiana.edu> wrote in message news:fd51e35e72ebd969092c577d7941d767@cs.indiana.edu...
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
Is it OK to make minor wording tweaks to the home page?
-- Fix missing "be" typo and TR2 clarification from Joe Gottman. -- Refine "Getting started" wording to make it clearer Boost works on Windows too.
Yes, go ahead. Doug
At 07:56 AM 8/2/2005, Beman Dawes wrote:
"Doug Gregor" <dgregor@cs.indiana.edu> wrote in message news:fd51e35e72ebd969092c577d7941d767@cs.indiana.edu...
Boost 1.33.0 release candidate #1 is now available here:
http://www.osl.iu.edu/~dgregor/boost-1.33.0/
There are two sets of files important for this release:
- boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats
Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc.
Is it OK to make minor wording tweaks to the home page?
-- Fix missing "be" typo and TR2 clarification from Joe Gottman. -- Refine "Getting started" wording to make it clearer Boost works on Windows too.
I've gone ahead and made these fixes. They were eating at me. --Beman
Doug Gregor wrote:
Boost 1.33.0 release candidate #1 is now available here:
Built OK on Fedora FC4 x86_64 using: ICU_PATH=/usr ICU_LINK="-licuuc -licui18n" PYTHON_ROOT=/usr PYTHON_VERSION=2.4 bjam -sTOOLS=gcc stage But, where are build options documented? I would have never figured out those ICU_PATH blah blah variables from the "Getting Started". Also, how do I determine whether my iostream build includes gzip/bzip? Where is this documented? I don't see it in the build instructions.
On Aug 2, 2005, at 11:30 AM, Neal Becker wrote:
Doug Gregor wrote:
Boost 1.33.0 release candidate #1 is now available here:
Built OK on Fedora FC4 x86_64 using: ICU_PATH=/usr ICU_LINK="-licuuc -licui18n" PYTHON_ROOT=/usr PYTHON_VERSION=2.4 bjam -sTOOLS=gcc stage
Glad to hear it.
But, where are build options documented? I would have never figured out those ICU_PATH blah blah variables from the "Getting Started". Also, how do I determine whether my iostream build includes gzip/bzip? Where is this documented? I don't see it in the build instructions.
John, Jonathan: Perhaps you two should updated the "Getting Started" guide with a note about these configuration options, and perhaps a link out to the documentation that describes them more fully. Doug
John, Jonathan: Perhaps you two should updated the "Getting Started" guide with a note about these configuration options, and perhaps a link out to the documentation that describes them more fully.
Done for regex. John.
"Doug Gregor" wrote:
Could a bzip2 compressed version be created? It would slash the size to one half and not everyone's on broadband. /Pavel
On Aug 2, 2005, at 1:19 PM, Pavel Vozenilek wrote:
"Doug Gregor" wrote:
Could a bzip2 compressed version be created? It would slash the size to one half and not everyone's on broadband.
There's a ".tar.bz2" that was compressed with bzip2. Did I miss something? Doug
"Douglas Gregor" wrote:
There's a ".tar.bz2" that was compressed with bzip2. Did I miss something?
Oops, apology. /Pavel
I'm using a Jamfile to link against the thread library and from the error message below it seems that there is a mismatch between what autolink expects (libboost_thread-vc71-mt-gd-1_33.lib) and what is actually compiled (boost_thread-vc71-mt-gd-1_33.lib). Does this ring a bell or should I prepare a minimal example that demonstrates the behavior? <error> ...\boost_1_33_0\libs\statechart\example>bjam "-sTOOLS=mingw vc-7_1" "-sMINGW_ROOT_DIRECTORY=C:\ProgramFiles\MinGW" ...found 1173 targets... ...updating 7 targets... vc-Link ..\..\..\bin\boost\libs\statechart\example\PingPongMulti1.exe\vc-7_1\debug\threading-multi\PingPongMulti1-vc71-mt-gd-1_33.exe LINK : fatal error LNK1104: cannot open file 'libboost_thread-vc71-mt-gd-1_33.lib' CALL "C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\VCVARS32.BAT" >nul "C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\link" /nologo /DEBUG /subsystem:console /out:"..\..\..\bin\boost\libs\statechart\example\PingPongMulti1.exe\vc-7_1\debug\threading-multi\PingPongMulti1-vc71-mt-gd-1_33.exe" /LIBPATH:"..\..\..\bin\boost\libs\thread\build\boost_thread.dll\vc-7_1\debug\threading-multi" "boost_thread-vc71-mt-gd-1_33.lib" @"..\..\..\bin\boost\libs\statechart\example\PingPongMulti1.exe\vc-7_1\debug\threading-multi\PingPongMulti1-vc71-mt-gd-1_33.CMD" ...failed vc-Link ..\..\..\bin\boost\libs\statechart\example\PingPongMulti1.exe\vc-7_1\debug\threading-multi\PingPongMulti1-vc71-mt-gd-1_33.exe... ...skipped <@boost!libs!statechart!example!run>PingPongMulti1-vc71-mt-gd-1_33.exe for lack of <@boost!libs!statechart!example\PingPongMulti1.exe\vc-7_1\debug\threading-multi>PingPongMulti1-vc71-mt-gd-1_33.exe... </error> -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
I'm using a Jamfile to link against the thread library and from the error message below it seems that there is a mismatch between what autolink expects (libboost_thread-vc71-mt-gd-1_33.lib) and what is actually compiled (boost_thread-vc71-mt-gd-1_33.lib). Does this ring a bell or should I prepare a minimal example that demonstrates the behavior?
Based on the error, autolink is looking for a static library, but you appear to want to link against the dll version, try defining BOOST_ALL_DYN_LINK when building to force autolink to look for the dll import library, and to ensure that the thread lib is correctly mangled with __declspec(dllimport) etc. John.
John Maddock wrote:
I'm using a Jamfile to link against the thread library and from the error message below it seems that there is a mismatch between what autolink expects (libboost_thread-vc71-mt-gd-1_33.lib) and what is actually compiled (boost_thread-vc71-mt-gd-1_33.lib). Does this ring a bell or should I prepare a minimal example that demonstrates the behavior?
Based on the error, autolink is looking for a static library, but you appear to want to link against the dll version, try defining BOOST_ALL_DYN_LINK when building to force autolink to look for the dll import library, and to ensure that the thread lib is correctly mangled with __declspec(dllimport) etc.
Ouch, my bad. What got me confused was that this works fine under 1.32 without the define BOOST_ALL_DYN_LINK. I guess it does because 1.32 only supports the dll variant of thread. 1.33 apparently now supports static and dynamic variants again... Thanks! Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
participants (1)
-
Aleksey Gurtovoy -
Andreas Huber -
Beman Dawes -
Doug Gregor -
Douglas Gregor -
Johannes Brunen -
John Maddock -
Jonathan Wakely -
Neal Becker -
Pavel Vozenilek -
Rene Rivera -
Sam Partington