Bear
Bear is a tool that generates a compilation database for clang tooling. (by rizsotto)
vscode-cmake-tools
CMake integration in Visual Studio Code (by microsoft)
Our great sponsors
Bear | vscode-cmake-tools | |
---|---|---|
50 | 7 | |
4,453 | 1,397 | |
- | 2.4% | |
5.7 | 9.1 | |
1 day ago | about 20 hours ago | |
C++ | TypeScript | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
Bear
Posts with mentions or reviews of Bear.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-17.
-
emacs lsp-mode with MPLAB X project
Have you tried Bear? I used it for several projects and overall it works very well.
-
Eglot + clangd not working for NetHack code base
An update: I am now able to make everything work by generating `compile_commands.json` using compiledb. I'm aware that there is another tool Bear but for some reason it generates an empty `compile_commands.json` file for me.
-
I have an existing legacy build system. How do I leverage this with CLion to index my project?
Try https://github.com/rizsotto/Bear
-
New User C Setup Help?
Regarding the libraries, you might need to add it to clangd’s configuration. A convenient way is to have a compile_commands.json in your project (this is generated by some build tools like CMake, but if you don’t use them, have a look at bear).
-
vscode alternative for C++ on M1 mac?
Note that you need to have a compile_commands.json file. That file can easily be generated by CMake, Meson, etc. For other build systems checkout Bear https://github.com/rizsotto/Bear
-
I hope that cscope can make a comeback in the versions after 0.9
make a 'gcc' command/executable that do nothing and make it first in your PATH and then run bear with make: https://github.com/rizsotto/Bear/issues/219 It is unfortunate that bear doesn't catch the output of the make command with '--dry-run' as it still prints the compile commands, it seems not that hard to support this and I think many ppl would benefit..
-
CLion 2023.1 released
You could try to start with Bear: https://github.com/rizsotto/Bear In worst cases, I had to use strace to catch every gcc/g++ invocation and restructure the compile_commands.json out of the strace logs.
-
Is CMake necessary to set up a C++ "IDE" in neovim?
But it sounds like maybe you’re assuming for the purposes of using something like clangd (highly recommended for coding in cpp projects in general, you want to be using this in vscode or whatever else anyway, codelion notwithstanding I suppose) with neovim on a c++ project that you have to use cmake to produce a compilation database to use with neovim plugins (e.g. clangd via nvim-lsp et. al.). In this case, be aware that the https://github.com/rizsotto/Bear tool is a handy way to just tack it on to whatever command you’re using to run a c++ code build step, and it will give you a compile_commands.json, corresponding to the compiler commands it invoked, on a silver platter.
-
Makefile versus CMake build system
I guess your questionmarks are about installing "bear", he refers to this project: https://github.com/rizsotto/Bear
-
how to use .clang-format with lunarvim ?
You just simply go to the root of your project, use bear and just open your C files. That's all.
vscode-cmake-tools
Posts with mentions or reviews of vscode-cmake-tools.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-08.
-
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.
What are some alternatives?
When comparing Bear and vscode-cmake-tools you can also consider the following projects:
compiledb - Tool for generating Clang's JSON Compilation Database files for make-based build systems.
prettier-vscode - Visual Studio Code extension for Prettier
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
Visual Studio Code - Visual Studio Code
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
Python - This extension is now maintained in the Microsoft fork.
scan-build - Clang's scan-build re-implementation in python
swift - The Swift Programming Language
coc-clangd - clangd extension for coc.nvim
Enterprise - Enterprise Engine
clangd - clangd language server
vetur - Vue tooling for VS Code.
Bear vs compiledb
vscode-cmake-tools vs prettier-vscode
Bear vs vscode-cpptools
vscode-cmake-tools vs Visual Studio Code
Bear vs NvChad
vscode-cmake-tools vs Python
Bear vs scan-build
vscode-cmake-tools vs swift
Bear vs coc-clangd
vscode-cmake-tools vs Enterprise
Bear vs clangd
vscode-cmake-tools vs vetur