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

How to build the latest release?
by Sinan 08 Nov '01

08 Nov '01

No matter what I try, ( I set JAMBASE, specified boost-base.jam etc... I always get the following error kanita% jam -f./tools/build/allyourbase.jam -sTOOLS="suncc" ./tools/build/allyourbase.jam: line 1608: syntax error at keyword ( don't know how to make all ...found 1 target... ...can't find 1 target... kanita% Line 1608 is the one that says: rule remember-binding ( target : bound-path ) { gBINDING($(target)) = $(bound-path) ; } ... How do I make jam understand the extended syntax ? ( Using FTjam 2.3.5 ...) Sinan Karasu ---------- # (C) Copyright David Abrahams 2001. Permission to copy, use, # modify, sell and distribute this software is granted provided this # copyright notice appears in all copies. This software is provided # "as is" without express or implied warranty, and with no claim as # to its suitability for any purpose. # compute directories for invoking WS6U2 WS6U2_BIN_DIRECTORY ?= $(WS6U2_ROOT_DIRECTORY)$(SLASH)bin ; WS6U2_BIN_DIRECTORY ?= "" ; # Don't clobber tool names if WS6U2_ROOT_DIRECTORY not set WS6U2_INCLUDE_DIRECTORY ?= $(WS6U2_ROOT_DIRECTORY)$(SLASH)include ; WS6U2_STDLIB_DIRECTORY ?= $(WS6U2_ROOT_DIRECTORY)$(SLASH)lib ; flags cc LINKFLAGS <runtime-link>static : -Bstatic ; flags cc CFLAGS <debug-symbols>on : -g ; flags cc LINKFLAGS <debug-symbols>on : -g ; flags cc CFLAGS <optimization>off : -xO0 ; flags cc CFLAGS <optimization>speed : -xO4 ; # Other optimizations we might want for WS6U2 # # flags cc CFLAGS <optimization>space : -xO2 ; flags cc CFLAGS <inlining>off : -xinline=no%func ; flags cc CFLAGS <inlining>on : -xinline=%auto ; flags cc CFLAGS <inlining>full : -xinline=%auto ; flags cc CFLAGS <profiling>on : -xpg ; flags cc LINKFLAGS <profiling>on : -xpg ; flags cc DEFINES <define> ; flags cc UNDEFS <undef> ; flags cc HDRS <include> ; flags cc STDHDRS : $(WS6U2_INCLUDE_DIRECTORY) ; flags cc STDLIBPATH : $(WS6U2_STDLIB_DIRECTORY) ; flags cc CFLAGS <shared-linkable>true : -KPIC ; flags cc LINKFLAGS <shared-linkable>true : -KPIC ; flags cc LINKFLAGS <target-type>DLL : -G ; flags cc LIBPATH <library-path> ; flags cc NEEDLIBS <library-file> ; flags cc FINDLIBS <find-library> ; #### Link #### rule Link-action { # This will appear before the import library name when building a DLL, but # will be "multiplied away" otherwise. The --exclude-symbols directive # proved to be neccessary with some versions of Cygwin. ##sik IMPLIB_COMMAND on $(<) = "-Wl,--exclude-symbols,_bss_end__:_bss_start__:_data_end__:_data_start__ -Wl,--out-implib," ; # IMPLIB_COMMAND on $(<) = "-Wl,--out-implib," ; cc-Link-action $(<) : $(>) ; } # for cc, we repeat all libraries so that dependencies are always resolved actions cc-Link-action bind NEEDLIBS { $(WS6U2_BIN_DIRECTORY)CC $(IMPLIB_COMMAND)$(<[2]) $(LINKFLAGS) -o "$(<[1])" -L$(LIBPATH) -L$(STDLIBPATH) "$(>)" "$(NEEDLIBS)" "$(NEEDLIBS)" -l$(FINDLIBS) -znodefs } # older actions # $(WS6U2_BIN_DIRECTORY)dlltool -e $(<[1]:S=:D=:G=) -l "$(<[2])" "$(>)" # $(WS6U2_BIN_DIRECTORY)CC $(LINKFLAGS) -L$(STDLIBPATH) "$(>)" "$(NEEDLIBS)" "$(NEEDLIBS)" -o "$(<[1])" #### Cc ##### rule Cc-action { cc-Cc-action $(<) : $(>) ; } actions cc-Cc-action { $(WS6U2_BIN_DIRECTORY)cc -c -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) -I$(BOOST_ROOT) -I"$(HDRS)" -I"$(STDHDRS)" -o "$(<)" "$(>)" } #### C++ #### rule C++-action { cc-C++-action $(<) : $(>) ; } actions cc-C++-action { $(WS6U2_BIN_DIRECTORY)CC -c -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) $(C++FLAGS) -I$(BOOST_ROOT) -I"$(HDRS)" -I"$(STDHDRS)" -o "$(<)" "$(>)" } #### Archive #### rule Archive-action { cc-Archive-action $(<) : $(>) ; } actions updated together piecemeal cc-Archive-action { ar ru "$(<)" "$(>)" } [Non-text portions of this message have been removed]

2 2

any question
by Thomas Matelich 08 Nov '01

08 Nov '01

In the docs, it uses a function called any_ptr, but I don't think it exists. Could someone please explain? -- Thomas O Matelich Senior Software Designer Zetec, Inc. matelich(a)home.com tmatelich(a)zetec.com

2 1

Boost release 1.25.1 now available
by Beman Dawes 07 Nov '01

07 Nov '01

Boost release 1.25.1 is now available at www.boost.org: * Boost Build System: Continued improvements. * Config Library: Continued refinements. * Graph Library: Final cleanup for upcoming the Boost Graph Library book. * Thread Library: Minor fixes - tests now pass on most Win32 and POSIX systems including Linux and Solaris. Semaphore removed as too error prone. * Function Library: direct support for member function pointers and documentation updates. * Boost-Users mailing list has been created to address topics of interest to users of Boost libraries. * Boost Wiki web added. Provides a place for Boost users to openly discuss and document the use of Boost libraries. It is not officially maintained by Boost developers. This release uses a new ftp program for updating the web site; the program used in the past was prone to get confused about dates, and didn't recover gracefully from network or server errors. Please let me know if you spot any out-of-date web pages on the site. --Beman

1 0

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