Changes between Initial Version and Version 1 of Ticket #35540, comment 5


Ignore:
Timestamp:
Dec 29, 2013, 5:04:43 AM (10 years ago)
Author:
lynxluna (Didiet)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35540, comment 5

    initial v1  
    66> So we can either think we're smarter than Google and install it anyway (and as a non-C++-programmer I don't feel competent to do that), or we can delete google-test from MacPorts.
    77
    8 When we write C++ code, we usually uses some compiler flags that specific to our need. This, as google pointed out on their [https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog FAQ entry] can cause problems. If gtest is compiled using macports flags and I use the flags that is slightly different or using different compiler, e.g. clang vs gcc, it can create a runtime problem. I usually end up just including all of gtest sources and build it directly on my test cases using the same compiler and the same compiler flags as the rest of my sources.
     8When we write C++ code, we usually use some compiler flags that specific to our need. This, as Google pointed out on their [https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog FAQ entry] can cause problems. If gtest is compiled using macports flags and I use the flags that is slightly different or using different compiler, e.g. `clang` vs `gcc`, it can create a runtime problem. I usually end up just including all of gtest sources and build it directly on my test cases using the same compiler and the same compiler flags as the rest of my sources.
    99
    1010I think it's wise to delete the `google-test` framework from macports as well as `gmock` as it depends on `google-gtest` and put the warning upon installation.