I've been reconsidering the use of bcp to import boost code into a public-facing portion of our api for intrusive_ptr, I've read the documentation somewhat, and tried using the command as follows:
C:\Program Files\boost\boost_1_41_0\>bcp intrusive_ptr ../../intrusive_ptr
What directory is it being run from? If it doesn't know where the Boost root directory is then the "intrusive_ptr" arg will be flagged as an error leading to the help screen. So either... use the --boost=path option to set the location of the boost tree, or else cd into Boost's root directory and:
bcp boost/intrusive_ptr.hpp destination-path
to get just the header and it's dependencies, or else:
bcp intrusive destination-path
to get all of the "intrusive" library and it's dependencies - including those of the example and test programs - ie quite a lot of code.
Using "intrusive_ptr" as a name failed, because there is no such library name in boost... it's spelled "intrusive" instead.
Do you mean smart_ptr instead of intrusive?
Ah, yes quite right, good catch! Thanks, John.