>> Did you test the specified make command for the display >> of expected data processing results? > > Markus, if something doesn't work, just say so, OK? Did a previous information fit to this expectation already? https://lore.kernel.org/linux-doc/c2c1dec0-2bd1-b0e2-1aa4-38d0e954d5ba@xxxxxx/ https://lkml.org/lkml/2020/6/30/492 “… make: Nothing to be done for 'path/to/file.c'. …” > Don't go all obtuse on us. I am curious if involved communication difficulties can be resolved better by other means. >> How much do you distinguish desired effects according to >> the specification of file extensions for such build commands? > > I don't grok that. I assume that you got used to the handling of specific file suffixes also for their application together with make scripts. One part of the discussed software documentation deals with the combination of compilation and further source code analysis, doesn't it? > Julia, Markus- can you tell me how to run coccicheck on one source file? You can choose between two methods. * Use the documented build target with appropriate parameters. (How many Linux software modules do consist of only a single source file?) * Do you get further ideas from another concrete command example? https://lore.kernel.org/linux-arm-kernel/5b693ee0-0cb1-7ff3-b562-bac6bcb6aae8@xxxxxx/ https://lkml.org/lkml/2020/6/29/357 elfring@Sonne:~/Projekte/Linux/next-patched> make J=1 C=1 CHECK='scripts/coccicheck' MODE=context COCCI=~/Projekte/Linux/next-patched/scripts/coccinelle/null/show_pointer_usage_before_null_check-20200701.cocci drivers/usb/mtu3/mtu3_gadget.o Regards, Markus
