use cmake build type defined in .travis.yml for travis builds

[ghost]

Currently, the BUILD_TYPE variable of .travis.yml was ignored up to now by travis.sh and the build process.

Also, while cmake does not complain on build type debug (as listed in .travis.yml currently), the cmake documentation always spells it Debug, so take this.

Using the variable in travis.sh to call cmake -DCMAKE_BUILD_TYPE=Debug leads to the problem reported in issue #1175, i.e. some Python driven tests won't find their test executable.

The travis build triggered by the first commits here will probably fail; then a fix can be tested and discussed.

This pull request fixes #1175 and #1070.

[ghost]

As expected, Travis build 853 is failing, i.e. CTest is failing with error messages as the following:

      Start 60: gtest_xml_output_unittest

60/60 Test #60: gtest_xml_output_unittest ...............***Failed    0.05 sec

Unable to find the test binary "/home/travis/build/google/googletest/build/googlemock/gtest/Debug/gtest_xml_output_unittest_". Please make sure to provide a path to the binary via the --build_dir flag or the BUILD_DIR environment variable.

The build type Debug was part of the path to the executable, which is wrong for this Cmake generator.
Trying to fix this now, though it might affect Windows which I'm unable to test currently - but AppVeyor will show it ...

[ghost]

Ok, unfortunately, ${CMAKE_CFG_INTDIR} is set during build only, not during test, so AppVeyor is complaining now. Seems we need a small switch here.

[ghost]

@gennadiycivil As soon as AppVeyor has finished, this is ready for review :-)

[gennadiycivil]

Looks mostly good to me - but can we add tests for positive proof?
It would be helpful to show simple test case "before" that was failing and then show same test "After"
I think you mostly have this , but if you could make it easier to review I would really appreciate it

[ghost]

@gennadiycivil - I already tried to create comments here in sequence to show this, sorry that it wasn't obvious enough.

The failing build is mentioned in this comment with a link to the build logs, after turning on the build type in travis.sh in commit cc246 - together with commit dae04 to use the CMake typical Debug instead of debug in .travis.yml. All Python based tests are failing, as the path given to Python is wrong.

The following commits, i.e. the changes in googletest/cmake/internal_utils.cmake, fix the build path given to Python. This path was o.k. for Windows, i.e. added e.g. Debug as postfix, but didn't work on UNIXoid systems which do not have split directories for multiple configurations in the build path.

[ghost]

Hmm, Travis build 888.6 timed out after a warning, probably not source code related? Will merge master into this branch to see the result of the next build.