Will Ware
Will Ware

Reputation: 505

Debugging or verbose mode for Kconfig?

I'm working with a LeopardBoard DM368 and I want to enable some video hardware. The relevant modules are vpfe-capture, isif, and tvp7002.

I've written a defconfig file with what I believe to be the correct set of CONFIG_FOO parameters for everything to work. Judging by the dependencies appearing in the various Kconfig files, I believe I've done everything correctly, but I can't seem to prevent kconf from discarding CONFIG_ISIF and CONFIG_VPFE_CAPTURE.

My very ugly alternative is to go in and start manually hacking makefiles. That works to pick up the modules I want, but it's obviously inconsistent with the design and intent of the Kconfig system, and would break any tools like "make gconfig".

make has a "-d" verbosity flag that explains how it is processing dependencies. Is there anything similar for kconf, where I could get it to explain why it's not giving me the two CONFIGs I'm trying to get?

Upvotes: 7

Views: 3622

Answers (2)

Ulf Magnusson
Ulf Magnusson

Reputation: 166

Sorry if this is a bit pluggish. :)

I've written a Python library for working with Kconfig-based configuration systems (Kconfiglib). It allows for easy inspection of symbol dependencies (see Symbol.__str__(), invoked e.g. by printing a Symbol) and lets you set values and evaluate arbitrary expressions in the context of a configuration, which can be handy to figure out what's going on.

Upvotes: 4

MikeK
MikeK

Reputation: 702

You could try running make V=2 oldconfig and see if that shows any additional clues.

Upvotes: 1

Related Questions