[pkg-boost-devel] boost dev tools

[Bernhard Reiter]

*ping*

anything i can do to get this fixed?

Bernhard

Am Mittwoch, den 03.06.2009, 16:47 +0200 schrieb Bernhard Reiter:
> Hi,
> 
> and thanks for the quick reply!
> 
> Am Dienstag, den 02.06.2009, 22:53 -0500 schrieb Steve M. Robbins:
> > I've had a very quick scan through the launchpad bug log and it
> > looks feasible.
> > 
> > Can I ask one thing?  
> > 
> > I'm not a user of these tools (boostbook, etc) so can you provide me
> > some examples with which I can test them?
> 
> Let me see...
> For boostbook and quickbook, both being documentation tools (the latter
> based upon the former), it's a natural test to have their own
> documentation built using the boost build system. 
> For inspect OTOH, which is a boost guideline sanity checker (with html
> output), you might just try to run it from any boost source code
> directory.
> 
> So, using a local copy of boost1.38-1.38.0:
> 
> * for boostbook: 
> cd tools/boostbook/doc
> bjam
> 
> That should generate boostbook docs in a new html subfolder from the xml
> files found in that folder.
> 
> * for inspect, why not
> cd tools/quickbook/
> inspect
> 
> which should give you html output about boost guideline violations in
> the quickbook source
> 
> * for quickbook: 
> cd tools/quickbook/doc
> bjam
> 
> Same as with boostbook, this time from quickbook.qbk.
> 
> ---
> 
> The one thing I'm rather unsure about are Depends and Suggests sections
> in debian/control, as there are a couple of optional features for
> boostbook (eg PDF output) and quickbook (eg doxygen documentation). See:
> http://www.boost.org/doc/libs/1_39_0/doc/html/boostbook/getting/started.html
> http://www.boost.org/doc/libs/1_39_0/doc/html/quickbook/install.html
> 
> ---
> 
> The one tool found in the list on http://www.boost.org/doc/ that I
> haven't packaged (and never really used) yet is regression. It generates
> 3 binaries in a directory that's named after the compiler used, and I'm
> not too seasoned in changing that. I only did some experimenting some
> time ago which lead me to believing that it would require a change in
> tools/regression/build/Jamroot.jam, appending
> 
> install dist-bin
>     :
>     process_jam_log
>     compiler_status
>     library_status
>     :
>     <install-type>EXE
>     <location>../../../dist/bin
>     :
>     release
>     ;
> 
> for those binaries to be built in a directory where they can be easily
> installed by debian/rules to usr/bin. So we might either go for that
> option or leave it for now as it is.
> 
> BTW, great work on packaging Boost -- and I'm looking forward to that
> boost-defaults scheme and the uncluttering of parallel boost1.3?
> versions...
> 
> HTH, and thanks again for the quick response!
> Bernhard