October 2001 - Boost-users - lists.preview.boost.org

Boost-Users announcement in 1.25.1
by Douglas Gregor 02 Nov '01

02 Nov '01

Hello all, We should announce the existence of the Boost-Users group in the 1.25.1 release of Boost. I've added a bullet to the "Latest News" entry for the release (just check index.htm in the top level of CVS). My two questions are: - Is there a more precise goal statement that should be in the announcement? (i.e., more precise that "address topics of interest to users of Boost libraries", which is intentionally vague) - Should we mention the Wiki? (with the usual not-Boost-moderated disclaimer) Doug

2 2

RE: [Boost-Users] array -v- array_traits
by Jim.Hyslop 25 Oct '01

25 Oct '01

Duane Murphy [SMTP:duanemurphy@mac.com] wrote: > I noticed that array.hpp uses > > #ifndef BOOST_ARRAY_HPP > #define BOOST_ARRAY_HPP > .. > #endif > > and array_traits.hpp uses: > > #if !defined(BOOST_ARRAY_HPP) > #define BOOST_ARRAY_HPP 1 > .. > #endif > > This means that you cant use them both at the same time? The first one wins? > > These are certainly similar classes but they dont seem to collide. > > Is this a subtle bug or intentional? Hi, Duane. I don't know the answer, but I've cc'd this to the Boost developer's list. Someone there should have an answer ;-) -- Jim Hyslop (moderator, Boost-Users group)

3 2

array -v- array_traits
by Duane Murphy 25 Oct '01

25 Oct '01

I noticed that array.hpp uses #ifndef BOOST_ARRAY_HPP #define BOOST_ARRAY_HPP .. #endif and array_traits.hpp uses: #if !defined(BOOST_ARRAY_HPP) #define BOOST_ARRAY_HPP 1 .. #endif This means that you cant use them both at the same time? The first one wins? These are certainly similar classes but they dont seem to collide. Is this a subtle bug or intentional? ..Duane

1 0

FW: [boost] any
by Jim.Hyslop 19 Oct '01

19 Oct '01

rajanikanth jammalamadaka [SMTP:rajanik3@rediffmail.com] wrote: > Hi! Jim, > Could you please tell me why this code is not working: > > #include <iostream> > #include <boost/any.hpp> > using namespace boost; > int main() > { > > any holdsanything ; > holdsanything = 9; > std::cout<<holdsanything<<endl; > holdsanything = std::string("hello"); > std::cout<<holdsanything<<endl; > return 0; > } Hi, Raj You didn't specify what problems you were having. Am I correct in assuming you get a compiler error on the std::cout lines? If so, then the problem is that class 'any' does not have an extraction operator defined. If you change the lines to: std::cout << any_cast<int>(holdsanything)<<std::endl; and std::cout << any_cast<const char *>(holdsanything) << std::endl; it should work properly. -- Jim

2 1

compiling boost on Win2k
by Mike Owens 19 Oct '01

19 Oct '01

I got a this suggestion from Damien Mulligan which worked really well. Use subst to map a drive letter to the path for the MSVC directory then use that drive letter in the VISUALC environment variable. Works like a charm. I should of thought of that. Thanks Damien. Mike > Date: Thu, 18 Oct 2001 08:12:05 -0400 > From: Anthony Kolarik <a.kolarik(a)computer.org> >Subject: RE: Digest Number 11 > >I don't have an answer for your specific JAM/Boost problem but I've seen >similar build problems (using cons)on NT and ended up using temp files to >hold the command line for the linker, rather than try to figure out why the >command lines worked fine on some machines and were too much for others. >You could look into registry settings to extend the buffer size for the >command interpreter but unless you can do it programmatically the temp file >approach would probably be a better. > -- Tony K.

1 0

RE: [Boost-Users] Digest Number 11
by Anthony Kolarik 18 Oct '01

18 Oct '01

I don't have an answer for your specific JAM/Boost problem but I've seen similar build problems (using cons)on NT and ended up using temp files to hold the command line for the linker, rather than try to figure out why the command lines worked fine on some machines and were too much for others. You could look into registry settings to extend the buffer size for the command interpreter but unless you can do it programmatically the temp file approach would probably be a better. -- Tony K. > Date: Wed, 17 Oct 2001 15:47:58 -0700 > From: Mike Owens <mikeo(a)medifor.com> > Subject: Build Problem > > I am trying to build boost on windows 2000 and I get "The > input line is too > long" errors. I have included some sample output from jam. > Please note I > switched to short file names to try and alleviate this > problem. Anyone have > any suggestions on overcoming this problem? > > "C:\Progra~1\micros~2\VC98"\bin\cl /Zm400 -nologo -GX -c > -DNDEBUG > -DBOOST_ > RE_NO_LIB=1 /O2 /GX /GR /MD -I"libs\regex\build" > -I"libs\regex\build\..\..\.. > " -I""C:\Progra~1\micros~2\VC98"\include" > -Fo"libs\regex\build\bin\libboost_re > gex.lib\msvc\release\runtime-link-dynamic\posix_api.obj" > -Tp"libs\regex\build\. > ./src\posix_api.cpp" > > ...failed msvc-C++-action > libs\regex\build\bin\libboost_regex.lib\msvc\release\r > untime-link-dynamic\posix_api.obj ... > msvc-C++-action > libs\regex\build\bin\libboost_regex.lib\msvc\release\runtime-lin > k-dynamic\regex.obj > The input line is too long. >

1 0

Build Problem
by Mike Owens 17 Oct '01

17 Oct '01

I am trying to build boost on windows 2000 and I get "The input line is too long" errors. I have included some sample output from jam. Please note I switched to short file names to try and alleviate this problem. Anyone have any suggestions on overcoming this problem? "C:\Progra~1\micros~2\VC98"\bin\cl /Zm400 -nologo -GX -c -DNDEBUG -DBOOST_ RE_NO_LIB=1 /O2 /GX /GR /MD -I"libs\regex\build" -I"libs\regex\build\..\..\.. " -I""C:\Progra~1\micros~2\VC98"\include" -Fo"libs\regex\build\bin\libboost_re gex.lib\msvc\release\runtime-link-dynamic\posix_api.obj" -Tp"libs\regex\build\. ./src\posix_api.cpp" ...failed msvc-C++-action libs\regex\build\bin\libboost_regex.lib\msvc\release\r untime-link-dynamic\posix_api.obj ... msvc-C++-action libs\regex\build\bin\libboost_regex.lib\msvc\release\runtime-lin k-dynamic\regex.obj The input line is too long.

1 0

How about a link to the burgeoning Wiki?
by Jon Kalb 16 Oct '01

16 Oct '01

I've added a Wiki link to the Group Bookmarks and also a link to the FAQ on the Wiki. We need to build that up. :) I also added a link to the Group Bookmarks page on the Group home page. ===== Jon Kalb Kalb(a)LibertySoft.com __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com

2 1

precompiled jam executables uploaded
by Toon Knapen 13 Oct '01

13 Oct '01

I just uploaded precompiled jam executables to the Files section for linuxx86, irix and solaris. I also added an InstallingBoost page to the Wiki with links to these executables. I hope this helps people with using the Boost.Build system. I gzip'ed the executables (except for the linux one) since I'm not sure if users find it a hassle to gunzip them first. It would safe space in the Files section though. People with jam executables for other platforms, please add them or transfer them to me so I can put them on there. toon

2 1

Building with Comeau
by Dale Peakall 12 Oct '01

12 Oct '01

Anyone had any success using the new build system with Comeau C++ on Win32 (MSVC6)? I'm using the pre-compiled Win32 jam binary from the FreeType project. Is this still suitable? I noticed Dave has checked in a whole bunch of changes to SourceForge. If not, is there an easy way to get the whole branch out of CVS? I've only ever used the web-interface which doesn't seem to provide this facility. The first problem I encountered was jam trying to use mv. After replacing the $(MV) instructions in the como-tools.jam with copy, I managed to get some obj files produced, but none of the libraries will link. First up, I noticed that the build system requires libcomo to be in a certain location, so I fixed that, but still nothing will link (lots of undefined external symbols - some to boost, some to std). I'm a Comeau newbie, so I may have messed up building libcomo (which would explain the missing std symbols), but not the missing boost symbols. Cheers, - Dale.

3 3