|
Boost : |
Subject: Re: [boost] [gsoc] Boost.Process done
From: Boris Schaeling (boris_at_[hidden])
Date: 2010-08-25 15:36:01
On Wed, 25 Aug 2010 00:27:35 +0200, John B. Turpish <jbturp_at_[hidden]>
wrote:
> [...]What's the minimum version of Boost it will work with? The latest
> version my employer has approved is 1.39 and I can see it doesn't work
> with that because UUID doesn't even exist.
I tested everything with 1.43.
In general Boost.Process depends on these header files from other Boost
C++ libraries:
boost/algorithm/string/predicate.hpp
boost/asio.hpp
boost/assert.hpp
boost/bind.hpp
boost/config.hpp
boost/filesystem/path.hpp
boost/lexical_cast.hpp
boost/make_shared.hpp
boost/noncopyable.hpp
boost/preprocessor/stringize.hpp
boost/ptr_container/ptr_unordered_map.hpp
boost/scoped_array.hpp
boost/shared_array.hpp
boost/shared_ptr.hpp
boost/system/config.hpp
boost/system/system_error.hpp
boost/thread.hpp
boost/throw_exception.hpp
boost/uuid/random_generator.hpp
boost/uuid/uuid.hpp
boost/uuid/uuid_io.hpp
If you don't include boost/process.hpp or boost/process/all.hpp though but
only those header files you need then boost/asio.hpp and a couple of
others are not required (if you don't do any asynchronous I/O for
example). But you are right that Boost.UUID is always required. The reason
is that a unique named pipe must be created if behavior::named_pipe is
used. If there are other ideas how to generate a unique name I can update
the code (Windows provides an API to generate UUIDs but unfortunately it
requires COM; on POSIX systems I'm not aware of any system function which
could generate UUIDs).
Boris
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk