We could bite the bullet and build [Quickbook] from source, I suppose.
There's something wrong with the DIST_BIN logic in Quickbook's Jamfile, because: D:\tmp2\boost>b2 tools/quickbook Performing configuration checks - 32-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) - symlinks supported : no (cached) - junctions supported : yes (cached) - hardlinks supported : yes (cached) ...patience... ...patience... ...found 3485 targets... ...updating 5 targets... common.mkdir D:\tmp2\boost\D:\tmp2 The filename, directory name, or volume label syntax is incorrect. if not exist "D:\tmp2\boost\D:\tmp2\\" mkdir "D:\tmp2\boost\D:\tmp2" ...failed common.mkdir D:\tmp2\boost\D:\tmp2... ...skipped D:\tmp2\boost\D:\tmp2\boost for lack of D:\tmp2\boost\D:\tmp2... ...skipped D:\tmp2\boost\D:\tmp2\boost\dist for lack of D:\tmp2\boost\D:\tmp2\boost... ...skipped D:\tmp2\boost\D:\tmp2\boost\dist\bin for lack of D:\tmp2\boost\D:\tmp2\boost\dist... ...skipped pD:\tmp2\boost\D:\tmp2\boost\dist\binquickbook.exe for lack of D:\tmp2\boost\D:\tmp2\boost\dist\bin... ...failed updating 1 target... ...skipped 4 targets... Also, the customary location for the build Jamfile is in build/, so that the usual invocation b2 tools/quickbook/build works, although that's a bit pedantic.