Hi, The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at: http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html These are generated after building documentation, which is not exactly the same as the final release, but it's close. Daniel
On 12/6/2012 1:17 AM, Daniel James wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them? -- Eric Niebler BoostPro Computing http://www.boostpro.com
If they are generated intermediate files why check them in at all? On Thu, Dec 6, 2012 at 12:35 PM, Eric Niebler <eric@boostpro.com> wrote:
On 12/6/2012 1:17 AM, Daniel James wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
-- Eric Niebler BoostPro Computing http://www.boostpro.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
(Rearranging...) On 12/6/2012 11:26 AM, Rene Rivera wrote:
On Thu, Dec 6, 2012 at 12:35 PM, Eric Niebler <eric@boostpro.com> wrote:
On 12/6/2012 1:17 AM, Daniel James wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
If they are generated intermediate files why check them in at all?
They're not. As Daniel says, he ran inspect after doing a doc build. This reduces the number of bogus "broken link" failures, but adds these others. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Ah I see. So ideally we would want to adjust the inspection to ignore generated files that are not included in a release package. Don't know how to do that though :-( On Thu, Dec 6, 2012 at 1:39 PM, Eric Niebler <eric@boostpro.com> wrote:
(Rearranging...)
On 12/6/2012 11:26 AM, Rene Rivera wrote:
On Thu, Dec 6, 2012 at 12:35 PM, Eric Niebler <eric@boostpro.com> wrote:
On 12/6/2012 1:17 AM, Daniel James wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
If they are generated intermediate files why check them in at all?
They're not. As Daniel says, he ran inspect after doing a doc build. This reduces the number of bogus "broken link" failures, but adds these others.
-- Eric Niebler BoostPro Computing http://www.boostpro.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On 6 December 2012 18:35, Eric Niebler <eric@boostpro.com> wrote:
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
Create a snapshot and run inspect over that. The script should be somewhere in tools/release.
On 12/6/2012 1:19 PM, Daniel James wrote:
On 6 December 2012 18:35, Eric Niebler <eric@boostpro.com> wrote:
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
Create a snapshot and run inspect over that. The script should be somewhere in tools/release.
??? Either you're confused or I am. How would creating a snapshot over here keep the inspect report from reporting problems over there ... or for anybody else who runs it in the future? -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 6 December 2012 23:52, Eric Niebler <eric@boostpro.com> wrote:
On 12/6/2012 1:19 PM, Daniel James wrote:
On 6 December 2012 18:35, Eric Niebler <eric@boostpro.com> wrote:
For the accumulators library, the xml files its complaining about are generated as part of the doc build. Is there some way to get inspect to ignore them?
Create a snapshot and run inspect over that. The script should be somewhere in tools/release.
??? Either you're confused or I am. How would creating a snapshot over here keep the inspect report from reporting problems over there ... or for anybody else who runs it in the future?
It won't, but that doesn't really matter. You don't want errors for the files because they're not included in a release. The only reliable way to tell that they aren't included in the release is to run the release scripts. We don't want to set inspect to ignore these files because if they were accidentally included in a release, inspect should complain. The ideal solution would be to change the build so that these files were placed somewhere under bin.v2, but that might not be realistic. On the other hand, there are a few false positives that no one cares about. Including you, since if you did, you would have noticed them years ago.
On 12/7/2012 8:39 AM, Daniel James wrote:
On the other hand, there are a few false positives that no one cares about. Including you, since if you did, you would have noticed them years ago.
Guilty as charged. ;-) -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Dec 6, 2012, at 1:17 AM, Daniel James <dnljms@gmail.com> wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
Just a reminder: there's nothing magical about the inspect tool - you can run it locally. Here's what I do: cd $BOOST/trunk/tools/inspect/build ; $BOOST/trunk/b2 cd $BOOST/trunk; $BOOST/trunk/dist/bin/inspect -deprecated_macro > $BOOST/snapshots/trunk-inspect.html ; open $BOOST/snapshots/trunk-inspect.html -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
On Dec 6, 2012, at 1:17 AM, Daniel James <dnljms@gmail.com> wrote:
Hi,
The snapshot builds and inspect results haven't been running for some time, so I've added running the inspect script to the documentation build for more up to date results. You can see them at:
http://boost.cowic.de/rc/docs-inspect-trunk.html http://boost.cowic.de/rc/docs-inspect-release.html
These are generated after building documentation, which is not exactly the same as the final release, but it's close.
Just a reminder: there's nothing magical about the inspect tool - you can run it locally. Here's what I do: cd $BOOST/trunk/tools/inspect/build ; $BOOST/trunk/b2 cd $BOOST/trunk; $BOOST/trunk/dist/bin/inspect -deprecated_macro > $BOOST/snapshots/trunk-inspect.html ; open $BOOST/snapshots/trunk-inspect.html -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
participants (4)
-
Daniel James -
Eric Niebler -
Marshall Clow -
Rene Rivera