http://blog.gmane.org/gmane.comp.lib.boost.documentation hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3597 _______________________________________________ Boost-docs mailing list Boost-docs< at >lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-docs vicente.botet 2008-11-19T20:02:52 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3596 Good evening list, my project (.c and .h, basically no c++) requires documentation in DocBook. In the past, I have been a contented user of doxygen. BoostBook has the capacity to generate DocBook .sgml from doxygen-annotated code, is that correct? My question: can I use BoostBook to generate DocBook .sgml from my doxygen-annotated header files without using Boost itself? If so, how? I have been trying to find my way in the Boost distro, but I didn't yet fathom its intricacies. Thanks, Rutger Hofman VU Amsterdam Rutger Hofman 2008-10-29T23:49:01 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3595 _______________________________________________ Boost-docs mailing list Boost-docs< at >lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-docs vicente.botet 2008-11-18T22:02:04 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3594 Quickbook is really just a simple text substitution engine. It does very little validation. But it's written with Spirit so it has a grammar. We could use the grammar to enforce *some* of the boostbook schema. For instance, we could change the grammar to enforce that anchors do not appear out of sections. Eric Niebler 2008-10-29T15:39:09 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3593 2008/10/27 John Maddock <john< at >johnmaddock.co.uk>: Sorry, I never got round to looking at this. I'm not sure but it's probably a quickbook bug. Quickbook has always generated invalid boostbook/docbook, but it's never been a problem before. I think the problem is that quickbook is generating boostbook along the lines of: <section>... <section>...</section> <anchor id="..." /> <para> </para> <section>...</section> </section> But anchors and paragraphs have to come before the sub-sections - they're not allowed between them. Which means that it's hard to generate valid boostbook for: [section ...] ... [endsect] A paragraph. [section ...] ... [endsect] But I think a solution is possible for your case: [section ...] ... [endsect] [#target] [section ...] ... [endsect] The anchor could be moved into the following section's title element which would be pretty close to the original intent. I'll create a ticket (and maybe try to implement this myself later). But in general, I don't think it's possible to generate valid boostbook without making quickbook a lot less flexible. Daniel Daniel James 2008-10-27T19:17:29 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3592 OK, I've got to the bottom of this, if you have a link target, say: [#my_target] in quickbook at top level scope (ie not inside a section) then you end up with an <fo:inline> tag generated for the target that is outside of any <fo:block>, and hense the invalid XML FO. I'm not sure if this is my bug, a quickbook issue, a docbook one, or an XSL one! :-( Whatever, for now it was easier to just change the quickbook markup so it generated valid XML. HTH, John. John Maddock 2008-10-27T16:24:55 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3591 I believe so yes: it appears to be an old issue not a new one as I first thought, John. John Maddock 2008-10-27T10:59:43 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3590 So what do we do? Work on trying to resolve the problem, but go ahead with 1.37.0 more or less on schedule even if it isn't resolved? 1.37.0 is scheduled for Friday. I don't currently know of any reason to delay, although I've still got a lot of unread email from the past weekend. --Beman Beman Dawes 2008-10-27T10:58:01 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3589 Experimenting some more: I see the problem on Boost-1.35 as well. I also note that I don't seem to have generated PDF's for Boost.Config previously, so I guess this may be an old issue after all.... John. John Maddock 2008-10-24T15:10:20 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3588 Hmmm, it's a weird one this: I had problems building on trunk, but not on the release branch about a month back, now I see the same results on both I *think*, but the problem is really capricious, sometimes it's there, sometimes it's not :-( I'm using release 6370 of the docbook xsl stylesheets *I think*. Probably I should update and try again, but I'm fairly sure it used to work... John. John Maddock 2008-10-24T15:06:19 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3587 2008/10/23 John Maddock <john< at >johnmaddock.co.uk>: I'm getting a similar error when I try building pdfs, but I'm also getting it when using boost 1.35 and 1.36. Which could be a problem with my setup (if the old versions still build for you, then it must be), or it might be that something has changed in the docbook xsl (not necessarily a bug, it could be an incorrect assumption in our stylesheets). Are you using a recent version? I'll experiment some more later on. I don't think any of the recent changes to boostbook would be likely to cause this, although I could have easily overlooked something. Daniel Daniel James 2008-10-24T13:54:56 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3585 Please, add a period at the end of the first sub-bullet, too (all entries have one in the qbk file). Pedantic-ly yours, Gennaro Prota 2008-10-18T15:15:59 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3584 OK (almost --I'm lost in all these dances :-) Please, can you replace the existing notes with the following? * [phrase library..[< at >/libs/dynamic_bitset/ Dynamic Bitset]:] * Constructor "do the right thing" dispatch, a la standard sequence containers (mimics the proposed resolution of [< at >http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#438 library issue 438], currently in the [^C++0x] working paper) * Improvements to documentation, code examples and implementation. If you are wondering what has changed, here we go: - the first link uses the "canonical" form libs/library_name/, without naming either index.htm[l] or dynamic_bitset.html; this is what I've been taught in the early days of Boost :-) If it doesn't work with the current website beta/upcoming/whoknows release arrangement feel free to change it back. - grammatically, both entries are "noun based"; mixing verb based and noun based entries was considered a severe error when I went at school (admittedly, some ten years ago) - "sequences" -> "sequence containers", the new name - link to description of lib issue 438 - removed "miscellaneous", which doesn't mean anything - perhaps something else nobody will ever want to know :-) The only reason I'm not doing this myself is that I don't have a working copy of the website tree and that setting up the documentation toolchain is a pain. It's a bless that you offered to take care of this. Thanks! Gennaro Prota 2008-10-18T15:11:28 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3583 2008/10/18 Gennaro Prota <gennaro.prota< at >yahoo.com>: Yes, the 1.37 documentation hasn't been uploaded yet. Daniel James 2008-10-18T13:40:06 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3582 Daniel, before sending you a little fix...: the "Dynamic Bitset" link leads to <http://beta.boost.org/doc/libs/1_36_0/libs/dynamic_bitset/dynamic_bitset.html> (with "1_36_0"). Is that normal? Gennaro Prota 2008-10-18T11:27:29 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3581 I have a working Win32 setup as well, as for maintaining it that's harder: not least because it's hard to tell when it's broken! The doxygen integration seems to be particulary flaky: often reporting success when it in fact failed, or at least mangled the output :-( John. John Maddock 2008-10-16T09:22:23 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3580 2008/10/13 Beman Dawes <bdawes< at >acm.org>: I don't know. I can't as I don't always have a windows machine. Daniel James 2008-10-13T18:19:31 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3579 Agreed. Who is the logical person to take responsibility? --Beman Beman Dawes 2008-10-13T15:04:20 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3578 The right place to ask this question would be the users list, where you'd probably get a better answer. But I'll try. 2008/10/13 Adem <for-gmane< at >alicewho.com>: There's a configure script at the root: http://svn.boost.org/svn/boost/trunk/configure If you run this it will create the makefile. Rather than use subversion, you'd probably be better of using an official release, but if you're using subversion the commands are something like: svn co http://svn.boost.org/svn/boost/trunk boost-trunk cd boost-trunk ./configure Note that this isn't an autoconf script and doesn't support all the options that most configure scripts do, it's more of a wrapper around the boost build system. Hope that helps, Daniel Daniel James 2008-10-13T09:32:01 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3577 The online documentation at http://www.boost.org/doc/libs/1_36_0/more/getting_started/unix-variants.html#link-your-program-to-a-boost-library says under section 5.1 "Easy Build and Install" that there is a configure and Makefile file, but in the svn trunk these files are missing. I wanted to use the filesystem library but it brings errors like "undefined reference to `boost::system::get_system_category()'" etc. How can I apply what is written in section 5.1 of the boost manual? Adem 2008-10-13T03:53:04 http://permalink.gmane.org/gmane.comp.lib.boost.documentation/3576 Odd... the other mail was sent almost 24 hours before the second one; I thought it had gone into the outer space (the more so because I had just subscribed to the documentation list). It seems instead that, as soon as I made another post, it "unblocked" :-) Well, I realized that it would be good to clarify (in the docs) a couple of details related to library issue 438; and that, accordingly, the release notices might need a tweak, too. That's why I thought to postpone everything to next week. Thanks, Gennaro Prota 2008-10-12T21:19:12 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lib.boost.documentation