Wrong setting for 'settings.compiler.libcxx' detected for gtest/1.8.1@bincrafters/stable

When trying to add dependency to gtest:

conan_cmake_run(
    REQUIRES
    gtest/1.8.1@bincrafters/stable
    BASIC_SETUP
    )

on call of

cmake .. -DCMAKE_BUILD_TYPE=Debug

I get:

-- Conan: Adjusting output directories
-- Conan: Using cmake global configuration
-- Conan: Adjusting default RPATHs Conan policies
-- Conan: Adjusting language standard
-- Current conanbuildinfo.cmake directory: /home/.../build-test-Debug
-- Conan: Compiler GCC>=5, checking major version 5
-- Conan: Checking correct version: 5
-- Conan: C++ stdlib: libstdc++
-- Conan: Automatic detection of conan settings from cmake
c++: error: $<$<CONFIG:Debug>:>: No such file or directory
c++: error: $<$<CONFIG:Release>:>: No such file or directory
c++: error: $<$<CONFIG:RelWithDebInfo>:>: No such file or directory
c++: error: $<$<CONFIG:MinSizeRel>:>: No such file or directory
-- Conan: Settings= -s;build_type=Debug;-s;compiler=gcc;-s;compiler.version=5;-s;compiler.libcxx=libc++
-- Conan executing: conan install . -s build_type=Debug -s compiler=gcc -s compiler.version=5 -s compiler.libcxx=libc++ -g=cmake
-- ERROR: Invalid setting 'libc++' is not a valid 'settings.compiler.libcxx' value.
Possible values are ['libstdc++', 'libstdc++11']
Read "http://docs.conan.io/en/latest/faq/troubleshooting.html#error-invalid-setting"

CMake Error at /home/.../cmake/conan.cmake:385 (message):
  Conan install failed='1'
Call Stack (most recent call first):
  /home/.../cmake/conan.cmake:465 (conan_cmake_install)
  /home/.../CMakeLists.txt:12 (conan_cmake_run)

Working on Ubuntu 16.04 LTS with default GCC (5.4.0).

[Yuri6037]

Any advancement on this issue? This prevents the build of cross platform projects and v0.14 minimum is required to support MSVC 2019.

[verbatom]

@Malacath-92: All observations and findings are listed in this issue including links to a duplicate and a pull request from October 2019 scheduled for milestone 0.16 to which is still open.

As mentioned in the answers of this issue, your current possibilities for dealing with the problem are the following:

1. revert to v0.13 until a fixed release version is available
2. locally patch your version of the file

[…] My bad, this issue refers to gtest […]

At least @theovin and I also referred to different projects in our bug reports instead of opening a new issue as the trigger for the problem might be different but the origin seemd to be the same.