vscode-cmake-tools
brokencppmap
vscode-cmake-tools | brokencppmap | |
---|---|---|
7 | 1 | |
1,397 | 0 | |
1.9% | - | |
9.1 | 10.0 | |
6 days ago | over 2 years ago | |
TypeScript | Rust | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-cmake-tools
-
Ask HN: Best book to learn C in 2022?
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.
- C++, CMake Tools, & IntelliSense: Red squiggles on #include in my headers
-
What is a “.dSYM” file??? I ran a c/cpp file, and it created more files when I ran it .... I’m running a M1 Mac on Monterey
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
-
I'm lost as to why GCC does not compile this file.
#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)
-
Debug and Release in different directories: build/debug build/release ?
source
-
trying to use a library
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 )
-
Now announcing: Makefile support in Visual Studio Code!
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.
brokencppmap
-
Ask HN: Best book to learn C in 2022?
Thanks for your response! I would edit to clarify but missed the edit window on my post.
> are you trying to call into C++ libraries from Rust/Swift using their FFI to C?
Yes. Examples (just POC, getting things to link and compile): <https://github.com/n8henrie/brokencppmap> <https://github.com/n8henrie/swiftcpp>
Thanks for the links -- I've been putting things together here and there from a combination of SO and the Rust user forum, which is why I was wondering about a more formal reference focused on this use case.
What are some alternatives?
Bear - Bear is a tool that generates a compilation database for clang tooling.
deno_bindgen - Write high-level Deno FFI libraries in Rust.
prettier-vscode - Visual Studio Code extension for Prettier
SwiftCPP
Visual Studio Code - Visual Studio Code
Python - This extension is now maintained in the Microsoft fork.
swift - The Swift Programming Language
Enterprise - Enterprise Engine
vetur - Vue tooling for VS Code.
SQLite - Official Git mirror of the SQLite source tree
sectorlisp - Bootstrapping LISP in a Boot Sector