Open GoogleCodeExporter opened 8 years ago
The GoogleTestConfig.cmake file should set up the library and include paths and
have a copy of internal_utils.cmake file, which when used via FIND_PACKAGE
makes those util functions/macros available for the user's CMakeLists.txt file.
Ideally there would be a build rule added to the existing cmake support for
building the gtest libs themselves that creates this GoogleTestConfig.cmake
file and points at the build dir for the libs to support using a locally-built
gtest.
Original comment by bruen...@google.com
on 6 Jun 2011 at 3:26
The official position is to have your CMake file refer to Google Test's one,
set appropriate flags, and use the library targets defined by Google Test
directly. See the discussion in
https://groups.google.com/d/topic/googletestframework/zHy-rrKz_Ho/discussion
for more info. It is a good idea to put it into a more prominent place like a
README, though.
Original comment by vladlosev
on 6 Jun 2011 at 6:49
Thanks Vlad!
Having it in the README would be indeed useful.
Original comment by timurrrr@google.com
on 7 Jun 2011 at 9:12
Original issue reported on code.google.com by
timurrrr@google.com
on 6 Jun 2011 at 3:13