Hi, What's the status for stopwatches? Because it's in chrono's metadata file, it's in the list at: http://www.boost.org/doc/libs/master/ Which will also put it in the release documentation list. But there's no documentation to link to, the headers don't get linked by 'b2 headers', and the tests don't seem to be running. Daniel
Le 14/07/14 09:31, Daniel James a écrit :
Hi,
What's the status for stopwatches? Because it's in chrono's metadata file, it's in the list at:
http://www.boost.org/doc/libs/master/
Which will also put it in the release documentation list. But there's no documentation to link to, the headers don't get linked by 'b2 headers', and the tests don't seem to be running.
Stopwatches has not been released yet. I merged the directory to the master branch to avoid discrepancies, but I could remove it if this is less confusing. Best, Vicente
On 14 July 2014 18:28, Vicente J. Botet Escriba
Le 14/07/14 09:31, Daniel James a écrit :
Hi,
What's the status for stopwatches? Because it's in chrono's metadata file, it's in the list at:
http://www.boost.org/doc/libs/master/
Which will also put it in the release documentation list. But there's no documentation to link to, the headers don't get linked by 'b2 headers', and the tests don't seem to be running.
Stopwatches has not been released yet. I merged the directory to the master branch to avoid discrepancies, but I could remove it if this is less confusing.
Strictly speaking, it probably shouldn't be there, but the metadata is the only real problem. I could add a field to indicate that a library is not released. Maybe by setting boost-version to false?
Le 14/07/14 19:35, Daniel James a écrit :
Le 14/07/14 09:31, Daniel James a écrit :
Hi,
What's the status for stopwatches? Because it's in chrono's metadata file, it's in the list at:
http://www.boost.org/doc/libs/master/
Which will also put it in the release documentation list. But there's no documentation to link to, the headers don't get linked by 'b2 headers', and the tests don't seem to be running.
Stopwatches has not been released yet. I merged the directory to the master branch to avoid discrepancies, but I could remove it if this is less confusing. Strictly speaking, it probably shouldn't be there, but the metadata is
On 14 July 2014 18:28, Vicente J. Botet Escriba
wrote: the only real problem. I could add a field to indicate that a library is not released. Maybe by setting boost-version to false?
Let me know if you need that I remove it. Best, Vicente
participants (2)
-
Daniel James
-
Vicente J. Botet Escriba