#3276 - Update README for make -n changes

This commit is contained in:
w0rp
2020-08-09 20:13:21 +01:00
parent 9e1f511003
commit bf3c3e9438

View File

@@ -816,12 +816,16 @@ setting. Consult the documentation for that setting for more information.
`b:ale_linters` can be used to select which tools you want to run, say if you `b:ale_linters` can be used to select which tools you want to run, say if you
want to use only `gcc` for one project, and only `clang` for another. want to use only `gcc` for one project, and only `clang` for another.
ALE will attempt to parse `make -n` when a `Makefile` is found or load the flags ALE will attempt to parse `compile_commands.json` files to discover compiler
for files from `compile_commands.json` files. See `:help g:ale_c_parse_makefile` flags to use when linting code. See `:help g:ale_c_parse_compile_commands` for
and `:help g:ale_c_parse_compile_commands` for more information. See Clang's more information. See Clang's documentation for
documentation for [compile_commands.json files](https://clang.llvm.org/docs/JSONCompilationDatabase.html). [compile_commands.json files](https://clang.llvm.org/docs/JSONCompilationDatabase.html).
You should strongly consider generating them in your builds, which is easy to You should strongly consider generating them in your builds, which is easy to do
do with CMake. with CMake.
You can also configure ALE to automatically run `make -n` to run dry runs on
`Makefile`s to discover compiler flags. This can execute arbitrary code, so the
option is disabled by default. See `:help g:ale_c_parse_makefile`.
You may also configure buffer-local settings for linters with project-specific You may also configure buffer-local settings for linters with project-specific
vimrc files. [local_vimrc](https://github.com/LucHermitte/local_vimrc) can be vimrc files. [local_vimrc](https://github.com/LucHermitte/local_vimrc) can be