June 2005 - Boost - lists.boost.org

[autolink] conflicts with new toolset names
by Joaquín Mª López Muñoz 13 Jun '05

13 Jun '05

autolink assumes the following toolset tags for libraries generated under the MSVC familiy of compilers: 6.0, 6.5 --> "v6" 7.0 --> "vc7" 7.1 --> "vc71" 8.0 --> "vc80" Yet tools/build/v1/boost-base.jam does the following: local include-minor-version = YES ; switch $(toolset) { case borland* : toolset-tag += bcb ; case como* : toolset-tag += como ; case cwpro8* : toolset-tag += cw 8 ; case cwpro9* : toolset-tag += cw 9 ; case cw-* : toolset-tag += cw ; include-minor-version = ; case darwin* : toolset-tag += ; case edg* : toolset-tag += edg ; case gcc* : toolset-tag += gcc ; case intel-linux* : toolset-tag += il ; case intel-win32* : toolset-tag += iw ; case kcc* : toolset-tag += kcc ; case kylix* : toolset-tag += bck ; case metrowerks* : toolset-tag += cw ; case mingw* : toolset-tag += mgw ; case mipspro* : toolset-tag += mp ; case msvc* : toolset-tag += vc 6 ; case sunpro* : toolset-tag += sw ; case tru64cxx* : toolset-tag += tru ; case vacpp* : toolset-tag += xlc ; case vc[678][_]* : { toolset-tag += vc ; toolset-tag += [ MATCH "vc([678])[_]([0123456789]*)" : $(toolset) ] ; } case vc[678]* : { toolset-tag += vc ; toolset-tag += [ MATCH "vc([678])" : $(toolset) ] ; } case * : toolset-tag += [ MATCH "^([^-]*)" : $(toolset) ] ; } if $(include-minor-version) { toolset-tag += [ MATCH "[-]([0123456789]+)[_.]([0123456789]*)" : $(toolset) ] ; } else { toolset-tag += [ MATCH "[-]([0123456789]+)[_.][0123456789]*" : $(toolset) ] ; } which does not match autolink expectations for the following toolsets adhering to the new naming conventions: vc-6_5 --> vc65 (expected vc6) vc-7_0 --> vc70 (expected v7) I guess it suffices to apply the following postrule in boost-base.jam switch $(toolset-tag) { case vc6* : toolset-tag = vc6 ; case vc70 : toolset-tag = vc7 ; } but someone more acquainted with bjam than me might come up with a nicer reformulation. Currently, this is breaking dozens of tests in the metacomm engine, which recently switched to vc-6_5-stlport and vc-7_0 toolsets. Do I commit this? Someone can tackle the issue more elegantly? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

meta-double
by Peder Holt 13 Jun '05

13 Jun '05

Is there any interest in a compile-time meta-version of double? Syntax: //Definition typedef META_DOUBLE(3.1415926535897932384626433) pi; //Or META_DOUBLE(3.1415926535897932384626433) pi_; //Mathematical operations typedef math::meta::add<pi,pi>::type pi2; //Evaluation: assert(META_DOUBLE_EVAL(pi2)==3.1415926535897932384626433*2); This implementation uses two ints to represent the decimals, and a short to represent the exponent. It has been tested on VC7.1,VC8.0 beta and GCC3.2 Regards, Peder

8 27

msvc-tools
by Victor A. Wagner Jr. 13 Jun '05

13 Jun '05

I changed the /EHsc to /EHac which seems to affect none of the tests excep the errors test on VC-8_0 which now works I've tested it with 7.1 and 8.0 I don't have any other complers btw, why is the /EHac (now) put in the command line twice? once as part of CFLAGS and once directly?? I just started another regression test....I'll be back before it finishes Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

2 1

logging library - minor bug report in "$yy" year formating
by Andy Schweitzer 13 Jun '05

13 Jun '05

Hello there, been playing with the logging library. Is this the right place to post bug reports? It seems that $yy prints "105" for the year 2005, not "05", which I expected. $yyyy is correct, it prints 2005. If line 173, // vals[m_yy + 1] = details.tm_year; is changed to // vals[m_yy + 1] = details.tm_year % 100; it appears to work... although I only tested with today's date.

2 1

logging library - v1.3.3
by John Torjo 13 Jun '05

13 Jun '05

Hi all, Just included the nifty appenders from Caleb, and made some small fixes. Enjoy! http://torjo.com/code/logging-v133.zip Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter) -- http://www.torjo.com/cb/ - Click, Build, Run!

2 2

IR is using boost
by Andrew Cameron 13 Jun '05

13 Jun '05

Name: PROGNOSIS IP Telephony Manager IP Telephony Express Company: Integrated Research P/L Description: PROGNOSIS is a suite of IP telephony management software products, specifically designed to address the key challenges of IP telephony life cycle management, including network-readiness, assessment, pre-deployment assurance testing, and ongoing Day-2 management of Cisco CallManager, Cisco Unity, and Cisco AVVID infrastructure. Boost Libs: boost.any boost.bind boost.function boost.lexical_cast boost.mpl boost.numeric_cast boost.ref boost.regex boost.smart_ptr boost.thread boost.thread_pool boost.type_traits URL: http://www.ir.com _____________________________________________________________________ This email is intended only for the use of the individual or entity named above and may contain information that is confidential and/or privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 9966 1066 and destroy the original message. Thank You _______________________________________________________________________

1 0

Help setting up boost for vc7
by Chris Ward 13 Jun '05

13 Jun '05

I have MS VC++ 7.1 installed to the default location (C:\Program Files\Microsoft Visual Studio .NET 2003), O/S WinXPSP2 However, when I run Build.bat from the command line, it returns " \Utilities\Bin\x86 was unexpected at this time." This occurs if I let the script auto-detect and also if I specify the toolset as vc7. Can someone please steer me in the right direction? regards Chris Ward

3 2

[thread] null_mutex
by Jody Hagins 13 Jun '05

13 Jun '05

Looking through the archives, a number of requests have been made for a null_mutex, but none exist. Probably because of the chance of trouble when used in conjunction with a condition variable. However, I have need for one (and it looks like others do as well, with a simple google search). Attached, are two files, each representing the output of running cvs diff on my local CVS repository (which is the official 1.32 release). diff.txt is the result of running: cvs -q diff diff-c.txt is the result of running: cvs -q diff -c I'd appreciate any feedback, and also consideration to add something like this to Boost.Thread.

5 12

Re: [boost] Pheonix-2 Debut
by Brian Braatz 12 Jun '05

12 Jun '05

> Super! How about the adaptable closures? I have to warn you though > that this may be a temporary bridge for Spirit 1.8 to Spirit 2.0. > Adaptable closures support may be retired in place of true local > variables (already supported in Phoenix 2); unless a solution > can be found to get rid of the nasty TLS ugliness in multithreaded > code. > > Regards, > -- > Joel de Guzman [Brian Braatz Writes:] If you would permit indulging my curiosity: :) I understand TLS. But I don't understand your problem? Is the problem because you need to use a global or static and when do you so, you are not thread safe (i.e. the classic getlasterror() problem with threads)?

2 1

[boostbook] building failed
by pedro.lamarao＠mndfck.org 12 Jun '05

12 Jun '05

With current CVS HEAD, following the instructions in the documentation, I get the following error. I tried reading the various Jamfile.v2 all over the place to try and understand what exactly I must pass to xsltproc to produce documentation manually but have had little success so far. [pedro@localhost doc]$ bjam-cvs --v2 Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). warning: Python location is not configured warning: the Boost.Python library won't be built warning: no toolsets are configured. warning: you won't be able to build C++ programs. warning: please consult the documentation. /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1259: in construct from module object(typed-target)@8 error: unable to construct ../libs/program_options/build/boost_program_options /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1142: in object(typed-target)(a)8.generate from module object(typed-target)@8 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:757: in generate-really from module object(main-target)@10 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:730: in object(main-target)(a)10.generate from module object(main-target)@10 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:886: in targets.generate-from-reference from module targets /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1080: in generate-dependencies from module object(typed-target)@24 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1121: in object(typed-target)(a)24.generate from module object(typed-target)@24 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:757: in generate-really from module object(main-target)@7 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:730: in object(main-target)(a)7.generate from module object(main-target)@7 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/tools/quickbook.jam:186: in object(quickbook-binary-generator)(a)1.run from module object(quickbook-binary-generator)@1 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/generators.jam:819: in try-one-generator-really from module generators /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/generators.jam:866: in try-one-generator from module generators /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/generators.jam:1073: in construct-really from module generators /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/generators.jam:1132: in generators.construct from module generators /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1256: in construct from module object(typed-target)@22 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1142: in object(typed-target)(a)22.generate from module object(typed-target)@22 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:757: in generate-really from module object(main-target)@5 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:730: in object(main-target)(a)5.generate from module object(main-target)@5 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:886: in targets.generate-from-reference from module targets /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1080: in generate-dependencies from module object(typed-target)@19 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:1118: in object(typed-target)(a)19.generate from module object(typed-target)@19 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:757: in generate-really from module object(main-target)@1 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:730: in object(main-target)(a)1.generate from module object(main-target)@1 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build/targets.jam:252: in object(project-target)(a)16.generate from module object(project-target)@16 /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/build-system.jam:196: in load from module build-system /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/kernel/modules.jam:259: in import from module modules /home/pedro/Workspace/boost/boost_HEAD/tools/build/v2/kernel/bootstrap.jam:153: in boost-build from module /home/pedro/Workspace/boost/boost_HEAD/boost-build.jam:12: in module scope from module

2 2