mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-11-29 16:41:27 +00:00
[docs] Clarify compile_flags.txt subtleties
See confusion e.g. in https://github.com/clangd/clangd/issues/637
This commit is contained in:
parent
be997cead7
commit
095f08653f
@ -94,6 +94,18 @@ to parse C++ code in the source tree.
|
||||
|
||||
Alternatives
|
||||
============
|
||||
For simple projects, Clang tools also recognize a compile_flags.txt file.
|
||||
This should contain one flag per line. The same flags will be used to compile
|
||||
any file.
|
||||
For simple projects, Clang tools also recognize a ``compile_flags.txt`` file.
|
||||
This should contain one argument per line. The same flags will be used to
|
||||
compile any file.
|
||||
|
||||
Example:
|
||||
|
||||
::
|
||||
|
||||
-xc++
|
||||
-I
|
||||
libwidget/include/
|
||||
|
||||
Here ``-I libwidget/include`` is two arguments, and so becomes two lines.
|
||||
Paths are relative to the directory containing ``compile_flags.txt``.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user