[Boost-docs] quickbook/filesystem and cygwin

Subject: [Boost-docs] quickbook/filesystem and cygwin
From: John Maddock (john_at_[hidden])
Date: 2008-12-06 16:31:20

OK I finally got around to trying a cygwin build of some docs, and didn't 
get very far:

* By default Boost.Filesystem expects Win32 paths when built under cygwin, 
but those paths don't work from within quickbook (which presumably expects 
or gets passed cygwin style paths?).  I see:

quickbook.quickbook-to-boostbook 
../../bin.v2/doc/test/gcc-mingw-3.4.4/debug/test.xml
Generating Output File: ../../bin.v2/doc/test/gcc-mingw-3.4.4/debug/test.xml
assertion "streams.empty()" failed: file 
"c:\data\boost\boost\trunk\tools\quickbook\detail\collector.cpp", line 46

* I modified quickbook so that it was built against a special 
Boost.Filesystem build that used cygwin paths and got the following error:

Starting program: 
/cygdrive/c/data/boost/boost/trunk/bin.v2/tools/quickbook/gcc-mingw-3.4.4/debug/link-static/quickbook.exe 
 -I"../.." --output-file="../../bin.v2/doc/test/gcc-mingw-3.4.4/debug/test.xml" 
"test.qbk"
[New thread 3012.0xfd4]
[New thread 3012.0xabc]
Generating Output File: ../../bin.v2/doc/test/gcc-mingw-3.4.4/debug/test.xml
assertion "base.is_complete() && (ph.is_complete() || !ph.has_root_name()) 
&& "boost::filesystem::complete() precondition not met"" failed: file 
"../../boost/filesystem/operations.hpp", line 577
      7 [sig] quickbook 3012 open_stackdumpfile: Dumping stack trace to 
quickbook.exe.stackdump

Anyone any ideas?

Cheers, John.