This is an archive of the discontinued LLVM Phabricator instance.

	Show First 20 Lines • Show All 1,027 Lines • ▼ Show 20 Lines

	And if the user want a finer-grained control for any reason, e.g., to scan the generated source files,			And if the user want a finer-grained control for any reason, e.g., to scan the generated source files,
	the user can choose to get the dependency information per file. For example:			the user can choose to get the dependency information per file. For example:

	.. code-block:: console			.. code-block:: console

	$ clang-scan-deps -format=p1689 -- <path-to-compiler-executable>/clang++ -std=c++20 impl_part.cppm -c -o impl_part.o			$ clang-scan-deps -format=p1689 -- <path-to-compiler-executable>/clang++ -std=c++20 impl_part.cppm -c -o impl_part.o

				.. warning::

				The ``<path-to-compiler-executable>/clang++`` should point to the real
				binary and not to a symlink. If it points to a symlink the include paths
				will not be correctly resolved.

	And we'll get:			And we'll get:

	.. code-block:: text			.. code-block:: text

	{			{
	"revision": 0,			"revision": 0,
	"rules": [			"rules": [
	{			{
	▲ Show 20 Lines • Show All 142 Lines • Show Last 20 Lines

[clang] Documents clang-scan-deps requirements.ClosedPublic