vscode-cmake-tools VS Python

After that I would recommend installing the MS CMake Tools extensions (https://github.com/microsoft/vscode-cmake-tools/blob/main/do...), this discovers CMakeLists.txt files in the projects and then uses those to setup build- and debugging targets, and in general gives your an IDE-like experience, while still being more transparent than a "fat IDE" like Visual Studio or Xcode.

what do you mean? you need to create a CMakeLists.txt file, the extension can create one for you iirc, take a look at: https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md

#https://medium.com/@onur.dundar1/cmake-tutorial-585dd180109b #https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md cmake_minimum_required(VERSION 3.0.0) project(Zoom VERSION 0.1.0) include(CTest) enable_testing() set(CMAKE_CXX_STANDARD 17) if(${CMAKE_BUILD_TYPE} MATCHES Debug) message("Debug Build") add_definitions(-DDEBUG="Debug Build") elseif(${CMAKE_BUILD_TYPE} MATCHES Release) message("Release Build") add_definitions(-DRELEASE="Release Build") endif() #benXml add_library(benXml STATIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/XmlRessource.cpp) target_sources(benXml PUBLIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/include/tinyxml2.cpp) #benLog FILE(GLOB_RECURSE benLog_all_sources "lib/benLog/*.cpp") add_library(benLog STATIC ${CMAKE_SOURCE_DIR}/lib/benLog/src/Log.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConfig.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConsoleTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogFileTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/Logger.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogLevel.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogTarget.cpp ) target_link_libraries(benLog benXml) #Zoom FILE(GLOB_RECURSE all_sources "src/*.cpp") add_executable(Zoom ${CMAKE_SOURCE_DIR}/src/Zoom.cpp) target_sources(Zoom PUBLIC ${all_sources}) target_include_directories(Zoom PUBLIC src lib) target_include_directories(Zoom PUBLIC src) target_link_libraries(Zoom mingw32) target_link_libraries(Zoom SDL2main) target_link_libraries(Zoom SDL2) target_link_libraries(Zoom SDL2_mixer) target_link_libraries(Zoom SDL2_image) target_link_libraries(Zoom SDL2_ttf) target_link_libraries(Zoom box2d) target_link_libraries(Zoom benXml) target_link_libraries(Zoom benLog) set(CPACK_PROJECT_NAME ${PROJECT_NAME}) set(CPACK_PROJECT_VERSION ${PROJECT_VERSION}) include(CPack)

source

It sounds like you don't have a version of make itself installed in your environment. If you're using msys2 as your environment, you might have hit this bug, which at least has a workaround (symbolic link from mingw32-make.exe to make.exe )

Hey, what issues are you seeing with the CMake Tools extension? My team would definitely like to make sure that these issues are tracked here Issues · microsoft/vscode-cmake-tools (github.com). We'll get to them as soon as we can to make sure folks have a great experience with Code regardless of the build system they're on.

The recommended fix in Troubleshooting Linting is to configure workspace settings to point to fully qualified python executable. I have done this, but the lint error remains.

But I mean, this doesn't prevent you from writing an open source extension that runs regardless of which version a user chooses to use, right? Users who are using the open source version of VS Code aren't forced to install the proprietary version with PyLance. The old extension is open source and even had a release just 18 hours ago - https://github.com/Microsoft/vscode-python