Jarrod Smith

I'm encountering the same issue. I'm on the latest flatbuffers vcpkg port ([2.0.0 port version 3](https://vcpkg.info/port/flatbuffers)) and flatbuffers npm 2.0.6. Would this help? https://github.com/microsoft/vcpkg/pull/24208

``` table RowData { id: uint16; pmask: uint32; payload: [uint8]; } struct RowUpdate { rows: [RowData]; } ``` I don't want `std::vector rows{};`, just a plain `std::vector`. But: Adding `(native_inline)`...

`-d yes` also gets difficult to interpret when there are nested sections within the tests. Not a viable workaround for this issue for my current projects unfortunately. The simple test-name-delineated...

I tried @bobbrow's suggestion but still no colours in the integrated terminal. I get colours if I run cmake manually from the integrated terminal command line though. 🤔

I see this behavior on Windows with MSVC / Ninja generator. ``` [cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of...

Commenting to avoid stale issue. I think this should be addressed.

@JackBoosY any workaround I can use for now?

I found a temporary workaround, passing `-DCMAKE_CXX_COMPILER:FILEPATH` in the OPTIONS of `vcpkg_configure_cmake()` inside the portfile.cmake: ``` cpkg_configure_cmake( SOURCE_PATH ${SOURCE_PATH} PREFER_NINJA OPTIONS -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/gcc-10.2/bin/c++ # TEMP: Workaround. Specify compiler. -DFLATBUFFERS_BUILD_TESTS=OFF -DFLATBUFFERS_BUILD_GRPCTEST=OFF ${OPTIONS}...

Alternative workaround, just for reference in case it helps track down a proper fix: 1. Put a comment in submodules/vcpkg/ports/flatbuffers/portfile.cmake so vcpkg recomputes the hash and will trigger a flatbuffers...

Any further thoughts on this?