Yes it does, and transparently too. There are only two differences compared to running under google-test.

crpcut requires version 1.4.0.

Call ::testing::InitGoogleMock(&argc, argv) before the call to crpcut::run(argc, argv). For example like:

    #include <gmock/gmock.h>
    #include <crpcut.hpp>

    int main(int argc, char *argv[])
    {
      ::testing::InitGoogleMock(&argc, argv);
      return crpcut::run(argc, argv);
    }

Does it look something like the below?

    /usr/lib/libgmock.so: undefined reference to `testing::AssertionSuccess()'
    /usr/lib/libgmock.so: undefined reference to `testing::InitGoogleTest(int*, char**)'
    /usr/lib/libgmock.so: undefined reference to `testing::internal::FormatForFailureMessage(char)'
    /usr/lib/libgmock.so: undefined reference to `testing::internal::String::Compare(testing::internal::String const&) const'

If so, you've forgotten to link with -lgtest. google-mock relies heavily on google-test, so even if you run the tests under crpcut you need to link with -lgtest to resolve all dependencies.

Time permitting, maybe, but it is not planned, and it's a major undertaking, so don't hold your breath waiting for it.