Digging into this further, it's pretty clear that the cmakebuilder plug-in is capturing the info we want, but doing it in the most proprietary way possible. It might be possible to modify it, but I think that's going well beyond the scope. Instead, I think I'll do the following:
take -01 then modify the pom settings a bit more so that we write TEST-nativetask-nttest.xml from gtest and nativetask-nttest.pstatus/stderr/stdout from cmakebuilder to surefire-reports. Then if we ever fix cmakebuilder to use the correct names/write junit/xunit xml, it'll be ready to go. Doing this also makes Jenkins and Yetus pick up the xml file and makes it slightly easier to find the output.
This still won't report the link error, of course, but it should allow for the rest of the test info to work correctly if those unit tests break.