Building gtest via CMake makes output incompatible with CMake's FindGTest.cmake module

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On Windows, build gtest via CMake.
2. Create another project via CMake, and use the FindGTest module that
comes with CMake 2.8, like so:
find_package (GTest REQUIRED)

What is the expected output? What do you see instead?
Expected output is that CMake is able to find all the correct libraries.
Instead, it doesn't find them, because the library naming and directory
layout is different for the CMake-built gtest versus the vcproj-built gtest.

The best solution would be to output a GTestConfig.cmake file that
specifies where the libraries and include directories are.

Please provide any additional information below, such as a code snippet.
For more info, see CMake bug here:
http://www.cmake.org/Bug/view.php?id=10229

Original issue reported on code.google.com by ben.med...@gmail.com on 12 Mar 2010 at 12:52

[GoogleCodeExporter]

Would you like to contribute the GTestConfig.cmake file?  Thanks.

Original comment by w...@google.com on 12 Mar 2010 at 8:11

• Changed state: Accepted
• Added labels: OpSys-All, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

GTest should be distributed with FindGTest.cmake file. Only GTest "knows" how 
to find 
its libraries.

Original comment by Dmitriy....@gmail.com on 25 Mar 2010 at 7:02

[GoogleCodeExporter]

See
https://groups.google.com/group/googletestframework/browse_thread/thread/668eff1
cebf5309d/f7787f381a418617?lnk=gst&q=harmful#f7787f381a418617

We consider it harmful/error-prone to distribute/install pre-compiled gtest
libraries.  Therefore I'm closing the issue as won't fix.

Original comment by w...@google.com on 25 Mar 2010 at 7:10

• Changed state: WontFix