From: Markus Elfring <Markus.Elfring@web.de>
To: Edgar Khachatryan <khachatryan.edgar@student.rau.am>
Cc: cocci@inria.fr, Ella Ma <xutong.ma@inria.fr>
Subject: Re: [cocci] Analyzing CMake Projects
Date: Tue, 18 Mar 2025 15:21:46 +0100 [thread overview]
Message-ID: <618afb48-b750-404d-98f2-d26a461fc357@web.de> (raw)
In-Reply-To: <CAN1=rvJBSpCq35PY-tTFomZ17wNBRN=bNV4vwKTV-TgYe38FdQ@mail.gmail.com>
…
> Additionally, I would like to know if there are any recommended ways to run Coccinelle on CMake-based projects.
It can occasionally be nicer to separate clarification approaches
for different issues.
> Is there an established method to integrate Coccinelle with CMake builds, or any workarounds you would suggest for analyzing such projects?
You can eventually benefit more from customised commands
and corresponding build targets.
https://cmake.org/cmake/help/v4.0/command/add_custom_command.html
Regards,
Markus
prev parent reply other threads:[~2025-03-18 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 14:39 [cocci] Detecting Use-After-Free and Analyzing CMake Projects Edgar Khachatryan
2025-03-18 9:43 ` Ella Ma
2025-03-18 13:45 ` [cocci] Detecting Use-After-Free … Markus Elfring
2025-03-18 14:21 ` Markus Elfring [this message]
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=618afb48-b750-404d-98f2-d26a461fc357@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=khachatryan.edgar@student.rau.am \
--cc=xutong.ma@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).