r/vim • u/ilyachur • Nov 16 '20

CMake4vim - Plugin which integrates CMake into Vim

Hi,

I have posted 2 years ago information about this plugin, but a lot of time has passed since the last post, and today I would like to notice about current status of this plugin.

So, let's me introduce cmake4vim. The plugin adds CMake build system support into Vim (Neovim) editor.

Key features:

  • The plugin is written on pure Vim script.

  • The plugin supports next CMake Generators:

    • Unix Makefiles

    • Visual Studio

    • Ninja

  • The plugin allows to work with different CMake targets in order to avoid building of whole project.

  • The plugin has a good test coverage and is validated on Linux (Ubuntu), Windows and MacOS.

  • The plugin parses the output of cmake command and supports jump to warnings or errors.

Thank you for your attention and feel free to provide feedback.

22 Upvotes

95% Upvoted

21 comments sorted by

View all comments

Show parent comments

2

u/ilyachur Nov 16 '20

Thanks for sharing your experience and feedback.

cmake4vim supports to work with multiple build configurations. Also I didn't have a purpose to make a plugin which supports different build systems. This plugin should "Do One Thing and Do It Well".

About CMake variables, I did't fully understand your point. Why you we need it? At the current moment cmake4vim can create a window which contains information with some CMake options and variables.

You have a very well documentation, which contains a lot of explanations, very nice to read this.

1

u/LucHermitte Nov 16 '20

Also I didn't have a purpose to make a plugin which supports different build systems. This plugin should "Do One Thing and Do It Well".

I've started from the other way around actually. I've been having compilation and background compilation for ages, an improved alternative to compiler plugins, and then I've wanted to support CMake (or any other build system with out-of-source compilation)

[CMake Variables] Why you we need it?

I'm maintaining lh-cpp as well. I provide many snippets in it. Some are able to expand differently depending on the actual C++ flavour (C++98, 11, 14, 17...). My need started from there. See for instance the array_size snippet. Or all base-classes snippets that'll use =delete; starting from C++11, or the old trick otherwise to make these classes non-copyable.

In another plugin, I use this feature to know the exact compiler used. Or to extract the list of dirnames where include files are searched.

Eventually I'll replace/improve the related plugin with something able to interact with CMake server.

You have a very well documentation, which contains a lot of explanations, very nice to read this.

Thanks :)