Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
Le 18/03/15 14:43, Edward Diener a écrit :
On 3/18/2015 5:49 AM, Paul A. Bristow wrote:
Do I have to rebuild the Boost.Test library to get the new docs ? Because the first thing I did was to try to view the new docs by opening index.html only to find that there was no html documentation. Then I tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received:
Performing configuration checks
- symlinks supported : yes error: Unable to find file or target named error: 'dyn_ut_example.cpp' error: referred to from project at error: '../../libs/test/example'
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation: http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html I do not know about the update frequency In order to build the doc: cd $boost/libs/test/doc ../../../bjam -sDOCBOOK_XSL_DIR=/some/path/docbook-xsl-1.78.1/ -sDOCBOOK_DTD_DIR=/some/path/docbook-xml-4.2/ Doxygen should be in the $PATH. The previous command will build whatever is necessary. Best, Raffi
On 3/18/2015 10:48 AM, Raffi Enficiaud wrote:
Le 18/03/15 14:43, Edward Diener a écrit :
On 3/18/2015 5:49 AM, Paul A. Bristow wrote:
Do I have to rebuild the Boost.Test library to get the new docs ? Because the first thing I did was to try to view the new docs by opening index.html only to find that there was no html documentation. Then I tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received:
Performing configuration checks
- symlinks supported : yes error: Unable to find file or target named error: 'dyn_ut_example.cpp' error: referred to from project at error: '../../libs/test/example'
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation:
http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html
I do not know about the update frequency
In order to build the doc: cd $boost/libs/test/doc ../../../bjam -sDOCBOOK_XSL_DIR=/some/path/docbook-xsl-1.78.1/ -sDOCBOOK_DTD_DIR=/some/path/docbook-xml-4.2/
Doxygen should be in the $PATH. The previous command will build whatever is necessary.
Thanks, I was able to build the docs and view them from the top-level index.html. Still the top-level jam file build should not be failing as it is doing in the 'develop' branch.
Le 18/03/15 16:37, Edward Diener a écrit :
Thanks, I was able to build the docs and view them from the top-level index.html.
Still the top-level jam file build should not be failing as it is doing in the 'develop' branch.
I left it there but I did not know if this is used by any tool (even if erroneous/not updated) or if there is any implicit convention for this file. So far it looks like it just triggers confusion. I will clean this up. Raffi
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: 18 March 2015 15:37 To: boost@lists.boost.org Cc: boost-users@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation:
http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html Thanks, I was able to build the docs and view them from the top-level index.html.
Still the top-level jam file build should not be failing as it is doing in the 'develop' branch.
I have built all the libraries, including test, from a recent clone of the whole modular-boost tree (as per getting started instructions apart from adding my choice of address-model and choosing asynch-exceptions: b2 address-model=32 architecture=x86 asynch-exceptions=on ) and can test things as expected. So that's pretty much 'works-for-me' ;-) And I think it would help if others can confirm this - thus reducing any risk from moving develop to master for the next release. Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 7542 2817 893
On 3/18/2015 12:15 PM, Paul A. Bristow wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: 18 March 2015 15:37 To: boost@lists.boost.org Cc: boost-users@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation:
http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html Thanks, I was able to build the docs and view them from the top-level index.html.
Still the top-level jam file build should not be failing as it is doing in the 'develop' branch.
I have built all the libraries, including test, from a recent clone of the whole modular-boost tree (as per getting started instructions apart from adding my choice of address-model and choosing asynch-exceptions: b2 address-model=32 architecture=x86 asynch-exceptions=on )
and can test things as expected.
So that's pretty much 'works-for-me' ;-)
And I think it would help if others can confirm this - thus reducing any risk from moving develop to master for the next release.
Am I supposed to be getting the latest Boost Build on 'develop' to do this ? Currently I have Boost Build on the 'master' branch. I was just reporting what I was getting when I executed b2 in the top-level Boost.Test directory. If the jam file is not supposed to be there it should be removed. I was able to execute b2 successfully in the Boost.Test build subdirectory.
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: 18 March 2015 17:37 To: boost@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
On 3/18/2015 12:15 PM, Paul A. Bristow wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: 18 March 2015 15:37 To: boost@lists.boost.org Cc: boost-users@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation:
http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html Thanks, I was able to build the docs and view them from the top-level index.html.
Still the top-level jam file build should not be failing as it is doing in the 'develop' branch.
I have built all the libraries, including test, from a recent clone of the whole modular-boost tree (as per getting started instructions apart from adding my choice of address-model and choosing asynch-exceptions: b2 address-model=32 architecture=x86 asynch-exceptions=on )
and can test things as expected.
So that's pretty much 'works-for-me' ;-)
And I think it would help if others can confirm this - thus reducing any risk from moving develop to master for the next release.
Am I supposed to be getting the latest Boost Build on 'develop' to do this ?
That was my suggestion - to try to find any remaining bugs only detectable by user (ab)use ;-) Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
AMDG On 03/18/2015 11:36 AM, Edward Diener wrote:
Am I supposed to be getting the latest Boost Build on 'develop' to do this ? Currently I have Boost Build on the 'master' branch.
I was just reporting what I was getting when I executed b2 in the top-level Boost.Test directory. If the jam file is not supposed to be there it should be removed.
From the errors that you're getting, I think
the error is in the Jamfile in the example subdirectory. Perhaps a file was not checked in?
I was able to execute b2 successfully in the Boost.Test build subdirectory.
In Christ, Steven Watanabe
Hi, First of all I am sorry for interfering with this tread, but I think it is the right place for asking the following question. I`m fairly new to the boost community and I would like to start contributing. Watching this mailing list for a couple of days, I couldn't help to notice that Boost.Test is an area that needs some additional "love", but I`m not sure where to start. I visited *http://tinyurl.com/l3sfpm4 http://tinyurl.com/l3sfpm4* , but as far as I can tell from this thread, some of them may be fixed in a separate branch. Can someone please give me some pinpoints on how to start this process? Regards, Serban Ungureanu
serban u
Hi, First of all I am sorry for interfering with this tread, but I think it is the right place for asking the following question. I`m fairly new to the boost community and I would like to start contributing. Watching this mailing list for a couple of days, I couldn't help to notice that Boost.Test is an area that needs some additional "love", but I`m not sure where to start.
Hi Serban, We've been working on finalizing the release lately and if you are still interested we can use some help to improve test coverage and overall improvement in test quality. Please ping me directly at rogeeff <at> gmail and we can discuss further details. Gennadiy
participants (6)
-
Edward Diener -
Gennadiy Rozental -
Paul A. Bristow -
Raffi Enficiaud -
serban u -
Steven Watanabe