public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Efremov <efremov@linux.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: What CONFIG_ option enables compilation of *.o file?
Date: Sat, 9 Jan 2021 21:20:34 +0300	[thread overview]
Message-ID: <17c5b8c7-80c4-c2b4-6eaf-704bfabb0a3c@linux.com> (raw)

Hi,

Is there a general way to get information about what CONFIG_ options
enable compilation of *.o (*.[ch]) file? Maybe with kconfig command or from
some generated files?

I mean, to get information that, for example:
1) driver/block/floppy.o depends on CONFIG_BLK_DEV_FD

From driver/block/Makefile:
	obj-$(CONFIG_BLK_DEV_FD)        += floppy.o

2) kernel/trace/trace_selftest_dynamic.o depends on CONFIG_FTRACE_SELFTEST

From kernel/trace/Makefile:
	ifdef CONFIG_FTRACE_SELFTEST
	obj-y += trace_selftest_dynamic.o
	endif

3) kernel/trace/trace_irqsoff.o depends on either CONFIG_IRQSOFF_TRACER
   or CONFIG_PREEMPT_TRACER

From kernel/trace/Makefile:
	obj-$(CONFIG_IRQSOFF_TRACER) += trace_irqsoff.o
	obj-$(CONFIG_PREEMPT_TRACER) += trace_irqsoff.o

4) drivers/dax/bus.o depends on CONFIG_DAX

From drivers/dax/Makefile:
	obj-$(CONFIG_DAX) += dax.o 
	dax-y += bus.o

5) drivers/soc/bcm/brcmstb/common.o depends on CONFIG_SOC_BRCMSTB

From drivers/Makefile:
	obj-y                           += soc/ 
From drivers/soc/Makefile:
	obj-y                           += bcm/
From drivers/soc/bcm/Makefile:
	obj-$(CONFIG_SOC_BRCMSTB)       += brcmstb/
From drivers/soc/bcm/brcmstb/Makefile
	obj-y += common.o 

Thanks,
Denis


             reply	other threads:[~2021-01-09 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 18:20 Denis Efremov [this message]
2021-01-14  6:45 ` What CONFIG_ option enables compilation of *.o file? Masahiro Yamada
2021-01-14  6:51   ` Randy Dunlap

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=17c5b8c7-80c4-c2b4-6eaf-704bfabb0a3c@linux.com \
    --to=efremov@linux.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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