From: Jani Nikula <jani.nikula@intel.com>
To: cocci@inria.fr
Subject: [cocci] spatch #include statements and include search path
Date: Mon, 13 Jan 2025 13:54:06 +0200 [thread overview]
Message-ID: <87plkrhqu9.fsf@intel.com> (raw)
I want to use a non-trivial match rule in multiple other rules, in
multiple .cocci files. I'm trying put the match rule in a separate file,
and #include that in the other files, to avoid duplication. (I'm
referring to the "include_cocci ::= #include string" usage of #include,
not transformations.)
It works when the current working directory is the same as the file to
be included, but I seem to be unable to make it work from another
directory.
It doesn't matter if the .cocci files are all in the same directory or
not, it doesn't seem to matter what I pass as -I to spatch on the
command-line. I see #include mentioned in the SmPL Grammar as well as
some tutorials, but I can't find any proper, working examples for it.
How is the #include and the search path supposed to work? There seems to
be some conflation in the documentation about include_cocci in .cocci
and #includes in the .c files.
Specifically, I'm running spatch in my kernel repo, and I keep the
.cocci files in a separate directory outside the kernel repo.
TIA,
Jani.
--
Jani Nikula, Intel
next reply other threads:[~2025-01-13 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 11:54 Jani Nikula [this message]
2025-01-13 12:09 ` [cocci] spatch #include statements and include search path Julia Lawall
2025-01-13 12:40 ` Jani Nikula
2025-01-13 12:43 ` Julia Lawall
2025-01-13 16:59 ` Jani Nikula
2025-01-14 17:50 ` Julia Lawall
2025-01-22 16:38 ` Victor Gambier
2025-01-23 13:21 ` Jani Nikula
2025-01-31 10:24 ` [cocci] [cocci-mirror] " Victor Gambier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plkrhqu9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=cocci@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).