113481Sgiacomo.travaglini@arm.comAs any non-trivial software system, Google Mock has some known limitations and problems. We are working on improving it, and welcome your help! The follow is a list of issues we know about. 213481Sgiacomo.travaglini@arm.com 313481Sgiacomo.travaglini@arm.com 413481Sgiacomo.travaglini@arm.com 513481Sgiacomo.travaglini@arm.com## README contains outdated information on Google Mock's compatibility with other testing frameworks ## 613481Sgiacomo.travaglini@arm.com 713481Sgiacomo.travaglini@arm.comThe `README` file in release 1.1.0 still says that Google Mock only works with Google Test. Actually, you can configure Google Mock to work with any testing framework you choose. 813481Sgiacomo.travaglini@arm.com 913481Sgiacomo.travaglini@arm.com## Tests failing on machines using Power PC CPUs (e.g. some Macs) ## 1013481Sgiacomo.travaglini@arm.com 1113481Sgiacomo.travaglini@arm.com`gmock_output_test` and `gmock-printers_test` are known to fail with Power PC CPUs. This is due to portability issues with these tests, and is not an indication of problems in Google Mock itself. You can safely ignore them. 1213481Sgiacomo.travaglini@arm.com 1313481Sgiacomo.travaglini@arm.com## Failed to resolve libgtest.so.0 in tests when built against installed Google Test ## 1413481Sgiacomo.travaglini@arm.com 1513481Sgiacomo.travaglini@arm.comThis only applies if you manually built and installed Google Test, and then built a Google Mock against it (either explicitly, or because gtest-config was in your path post-install). In this situation, Libtool has a known issue with certain systems' ldconfig setup: 1613481Sgiacomo.travaglini@arm.com 1713481Sgiacomo.travaglini@arm.comhttp://article.gmane.org/gmane.comp.sysutils.automake.general/9025 1813481Sgiacomo.travaglini@arm.com 1913481Sgiacomo.travaglini@arm.comThis requires a manual run of "sudo ldconfig" after the "sudo make install" for Google Test before any binaries which link against it can be executed. This isn't a bug in our install, but we should at least have documented it or hacked a work-around into our install. We should have one of these solutions in our next release.