On 2015-05-22 1:28 AM, Joshua Cranmer 🐧 wrote:
3. OS X builds use clang, which should interoperate with gcc's method,
but it does cause either a link error (in opt) or a runtime loader issue
(in debug). I think a newer version of clang would fix the issues, but
I've been unable to figure out how
It's not sufficient, but it's enough to start building tooling around.
Any future platforms will upload the data to the same places and in the
same format. So anything that uses the data will be easier to generalize
to additional platforms as they become available.
I can start work scheduling
On 5/21/2015 11:38 AM, Andrew Halberstadt wrote:
If someone figures out how to generate code coverage data on
Windows/OSX, I'd be happy to take care of the scheduling pieces. Beyond
that, I personally don't have any plans to work further on code
coverage. If you want to take a shot at generating
For those with an interest in exploring C++ code coverage, it is now
easy to generate coverage files on try. This *does not* mean that code
coverage reports are readily available, or that they will be anytime
soon. This is only useful for people who are interested in creating
reports themselves.
4 matches
Mail list logo
