[bitfield] documentation does not build
2.6 <threadapi>win32 error: removed properties: none C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:490: in actualize-no-scanner from module object(file-target)@1078 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:135: in object(file-target)@1078.actualize from module object(file-target)@1078 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:811: in actualize-source-type from module object(action)@1087 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:832: in actualize-sources from module object(action)@1087 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:759: in object(action)@1087.actualize from module object(action)@1087 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:311: in actualize-action from module object(file-target)@1088 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:499: in actualize-no-scanner from module object(file-target)@1088 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:135: in object(file-target)@1088.actualize from module object(file-target)@1088 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:811: in actualize-source-type from module object(action)@1092 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:832: in actualize-sources from module object(action)@1092 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:759: in object(action)@1092.actualize from module object(action)@1092 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:311: in actualize-action from module object(file-target)@1093 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:499: in actualize-no-scanner from module object(file-target)@1093 C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:135: in object(file-target)@1093.actualize from module object(file-target)@1093 C:/Programming/VersionControl/boost/tools/build/v2\build-system.jam:748: in load from module build-system C:\Programming\VersionControl\boost\tools\build\v2/kernel\modules.jam:283: in im
My mistake: it should be the bitfield library, not bitset. Attempting to build the documentation for bitfield, I get a bunch of errors: "C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:1079 : in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p..\..\..\bin.v2\libs\integer\doc\msvc- 10.0\debug\threading-multi>bitfield.xml error: previous virtual target { quickbook%quickbook.quickbook-to-boostbook-bitf ield.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: another virtual target { quickbook%quickbook.quickbook-to-boostbook-bitfi eld.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: added properties: <preserve-test-targets>on <python-debugging>off <python port from module modules C:\Programming\VersionControl\boost\tools\build\v2\kernel\bootstrap.jam:142: in boost-build from module C:\Programming\VersionControl\sandbox\boost-build.jam:66: in module scope from m odule" The docs need to be buildable for anyone to use the library or be willing to review it.
On 01/15/2011 04:03 PM, Edward Diener wrote:
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors:
"C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:1079
: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p..\..\..\bin.v2\libs\integer\doc\msvc- 10.0\debug\threading-multi>bitfield.xml error: previous virtual target { quickbook%quickbook.quickbook-to-boostbook-bitf ield.xml.XML { bitfield.qbk.QUICKBOOK } }
<snip>
The docs need to be buildable for anyone to use the library or be willing to review it.
Do you have the toolchain installed? Quickbook, Boostbook, possibly Doxygen .... all the parts that need to be there. See : <http://www.boost.org/doc/libs/1_45_0/doc/html/quickbook/install.html> Also ... setting up the documentation chain isn't for the faint-of-heart. Most people just use pre-generated versions. michael -- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com
On 1/15/2011 7:18 PM, Michael Caisse wrote:
On 01/15/2011 04:03 PM, Edward Diener wrote:
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors:
"C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:1079
: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p..\..\..\bin.v2\libs\integer\doc\msvc- 10.0\debug\threading-multi>bitfield.xml error: previous virtual target { quickbook%quickbook.quickbook-to-boostbook-bitf ield.xml.XML { bitfield.qbk.QUICKBOOK } }
<snip>
The docs need to be buildable for anyone to use the library or be willing to review it.
Do you have the toolchain installed? Quickbook, Boostbook, possibly Doxygen .... all the parts that need to be there.
Yes. It's all there.
----- Original Message ----- From: "Edward Diener" <eldiener@tropicsoft.com> To: <boost@lists.boost.org> Sent: Sunday, January 16, 2011 1:03 AM Subject: [boost] [bitfield] documentation does not build
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors: <snip> The docs need to be buildable for anyone to use the library or be willing to review it.
Hi, I had not rebuilt the doc since 3 Mai 2009. I have copied the directory bitfield on the trunk/libs and I have no problems building it even the pdf. Could you show from which directory hierarchy are you building? Vicente@viboes1 /boost/trunk2/libs/bitfield/libs/integer/doc $ bjam ...found 23 targets... ...updating 9 targets... common.mkdir ../../../../../bin.v2/libs/bitfield common.mkdir ../../../../../bin.v2/libs/bitfield/libs common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4 common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/debu g quickbook.quickbook-to-boostbook ../../../../../bin.v2/libs/bitfield/libs/intege r/doc/gcc-3.4.4/debug/bitfield.xml Generating Output File: ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc -3.4.4/debug/bitfield.xml xslt-xsltproc ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/deb ug/bitfield.docbook xslt-xsltproc-dir html/standalone_HTML.manifest Computing chunks... Writing standalone_HTML.manifest ...updated 9 targets... Best, Vicente
On 1/16/2011 4:30 AM, vicente.botet wrote:
----- Original Message ----- From: "Edward Diener"<eldiener@tropicsoft.com> To:<boost@lists.boost.org> Sent: Sunday, January 16, 2011 1:03 AM Subject: [boost] [bitfield] documentation does not build
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors: <snip> The docs need to be buildable for anyone to use the library or be willing to review it.
Hi,
I had not rebuilt the doc since 3 Mai 2009. I have copied the directory bitfield on the trunk/libs and I have no problems building it even the pdf. Could you show from which directory hierarchy are you building?
I retrieved the bitfield library from the vault, which is the link given on the review schedule page at http://www.boost.org/community/review_schedule.html . After getting bitfield from the vault as a zip file, I expanded it into its own directory beneath the main sandbox directory, went to its libs/integer/doc directory and ran: bjam --boost=path/to/boost toolset=msvc-10.0 where the path/to/boost points to the latest version in the trunk. I received the errors in my original post. I also see there is another libs/integer in Boost, so that I think you must rename your own subdirectory to 'bitfield' instead. I do not know why you chose 'integer'. I think you should be following the recommended directory structure for sandbox libraries even if your library is in the vault instead.
Vicente@viboes1 /boost/trunk2/libs/bitfield/libs/integer/doc $ bjam ...found 23 targets... ...updating 9 targets... common.mkdir ../../../../../bin.v2/libs/bitfield common.mkdir ../../../../../bin.v2/libs/bitfield/libs common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4 common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/debu g quickbook.quickbook-to-boostbook ../../../../../bin.v2/libs/bitfield/libs/intege r/doc/gcc-3.4.4/debug/bitfield.xml Generating Output File: ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc -3.4.4/debug/bitfield.xml xslt-xsltproc ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/deb ug/bitfield.docbook xslt-xsltproc-dir html/standalone_HTML.manifest Computing chunks... Writing standalone_HTML.manifest ...updated 9 targets...
Best, Vicente _______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
----- Original Message ----- From: "Edward Diener" <eldiener@tropicsoft.com> To: <boost@lists.boost.org> Sent: Sunday, January 16, 2011 2:11 PM Subject: Re: [boost] [bitfield] documentation does not build
On 1/16/2011 4:30 AM, vicente.botet wrote:
----- Original Message ----- From: "Edward Diener"<eldiener@tropicsoft.com> To:<boost@lists.boost.org> Sent: Sunday, January 16, 2011 1:03 AM Subject: [boost] [bitfield] documentation does not build
I had not rebuilt the doc since 3 Mai 2009. I have copied the directory bitfield on the trunk/libs and I have no problems building it even the pdf. Could you show from which directory hierarchy are you building?
I retrieved the bitfield library from the vault, which is the link given on the review schedule page at http://www.boost.org/community/review_schedule.html .
After getting bitfield from the vault as a zip file, I expanded it into its own directory beneath the main sandbox directory, went to its libs/integer/doc directory and ran:
bjam --boost=path/to/boost toolset=msvc-10.0
where the path/to/boost points to the latest version in the trunk. I received the errors in my original post.
I also see there is another libs/integer in Boost, so that I think you must rename your own subdirectory to 'bitfield' instead. I do not know why you chose 'integer'. I think you should be following the recommended directory structure for sandbox libraries even if your library is in the vault instead.
I followed the same schema than Boost.Endian as both libraries should be part of Boost.Integer. But I understand that the documentation needs to renamed. Best, Vicente
On 1/16/2011 4:30 AM, vicente.botet wrote:
----- Original Message ----- From: "Edward Diener"<eldiener@tropicsoft.com> To:<boost@lists.boost.org> Sent: Sunday, January 16, 2011 1:03 AM Subject: [boost] [bitfield] documentation does not build
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors: <snip> The docs need to be buildable for anyone to use the library or be willing to review it.
Hi,
I had not rebuilt the doc since 3 Mai 2009. I have copied the directory bitfield on the trunk/libs and I have no problems building it even the pdf. Could you show from which directory hierarchy are you building?
Vicente@viboes1 /boost/trunk2/libs/bitfield/libs/integer/doc $ bjam ...found 23 targets... ...updating 9 targets... common.mkdir ../../../../../bin.v2/libs/bitfield common.mkdir ../../../../../bin.v2/libs/bitfield/libs common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4 common.mkdir ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/debu g quickbook.quickbook-to-boostbook ../../../../../bin.v2/libs/bitfield/libs/intege r/doc/gcc-3.4.4/debug/bitfield.xml Generating Output File: ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc -3.4.4/debug/bitfield.xml xslt-xsltproc ../../../../../bin.v2/libs/bitfield/libs/integer/doc/gcc-3.4.4/deb ug/bitfield.docbook xslt-xsltproc-dir html/standalone_HTML.manifest Computing chunks... Writing standalone_HTML.manifest ...updated 9 targets...
It is my fault. I had not realized that it was a sandbox library and I needed to get an update after bringing it down from the vault.
AMDG On 1/15/2011 4:03 PM, Edward Diener wrote:
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors:
"C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:1079
: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p..\..\..\bin.v2\libs\integer\doc\msvc- 10.0\debug\threading-multi>bitfield.xml error: previous virtual target { quickbook%quickbook.quickbook-to-boostbook-bitf ield.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: another virtual target { quickbook%quickbook.quickbook-to-boostbook-bitfi eld.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: added properties: <preserve-test-targets>on <python-debugging>off <python
2.6 <threadapi>win32 error: removed properties: none
This a Boost.Build problem that manifests itself when a property is defined after a target has already been processed. You can work around it by making sure that that the boost Jamfiles are loaded sooner. In Christ, Steven Watanabe
On 1/16/2011 6:44 PM, Steven Watanabe wrote:
AMDG
On 1/15/2011 4:03 PM, Edward Diener wrote:
My mistake: it should be the bitfield library, not bitset.
Attempting to build the documentation for bitfield, I get a bunch of errors:
"C:/Programming/VersionControl/boost/tools/build/v2/build\virtual-target.jam:1079
: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p..\..\..\bin.v2\libs\integer\doc\msvc- 10.0\debug\threading-multi>bitfield.xml error: previous virtual target { quickbook%quickbook.quickbook-to-boostbook-bitf ield.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: another virtual target { quickbook%quickbook.quickbook-to-boostbook-bitfi eld.xml.XML { bitfield.qbk.QUICKBOOK } } error: created from ./bitfield error: added properties: <preserve-test-targets>on <python-debugging>off <python
2.6 <threadapi>win32 error: removed properties: none
This a Boost.Build problem that manifests itself when a property is defined after a target has already been processed. You can work around it by making sure that that the boost Jamfiles are loaded sooner.
The actual bjam file involved was for Vicente Botet Escriba's bitfield library so maybe he will read your reply and make the appropriate changes if he still has to. Once I did an SVN update on his library, the documentation was already there and so I did not try to build it again. Needless to say his jamfile should be correct but my goal was just to read the docs for bitfield.
participants (4)
-
Edward Diener -
Michael Caisse -
Steven Watanabe -
vicente.botet