Compile problem using IoStreams from CVS inside boost v1.32 (VC71)

I am using VC7.1 (and will also be using VC70 for this code) What I did- Executed the following from a cmd prompt: cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost checkout boost cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout went into boost\iostreams and boost\libs\iostreams- copied both into temp area- Deleted the CVS folders Copied the files into the boost 1.32 dir in my company's internal CVS server (we have the boost files under revision control to control which version of which file we are using to build) Initially I had to change the files to from namespace io to iostreams. Got through those compile errors. And Now I have this one: boost\algorithm\string\iterator_range.hpp(288) : error C2874: using-declaration causes a multiple declaration of 'boost::algorithm::iterator_range' \boost\algorithm\string\iterator_range.hpp(204) : see declaration of 'boost::algorithm::iterator_range' I am digging into this but thought I would throw this out to see if any one is aware of the issue- These errors point to the end of iterator_range.hpp (pointing at the using clause) Here is a snippet from that file: template< typename SeqT, typename IteratorT, typename FuncT > inline SeqT transform_iterator_range( const iterator_range<IteratorT>& Range, FuncT Func ) { SeqT Seq; std::transform( Range.begin(), Range.end(), std::back_inserter(Seq), Func ); return Seq; } } // namespace algorithm // pull names to the namespace boost using algorithm::iterator_range; using algorithm::make_iterator_range; using algorithm::copy_iterator_range; using algorithm::transform_iterator_range; } // namespace boost

Brian Braatz wrote:
I am using VC7.1 (and will also be using VC70 for this code)
What I did-
Copied the files into the boost 1.32 dir in my company's internal CVS server (we have the boost files under revision control to control which version of which file we are using to build)
I don't want to discourage you from trying to solve these problems; if you manage to get the CVS iostreams working with 1.32 be sure to post the result here, since others may be interested. However, my sole concern now is getting iostreams to work with the current Boost CVS on all the supported platforms, especially since there are some features I want to add before the release. Jonathan
participants (2)
-
Brian Braatz
-
Jonathan Turkanis