[Solved]-How do I make Eclipse recognize KBUILD_MODNAME?-eclipse

[everything below is based on kernel 4.15.0]

forming of kbuild_modname can be understood by looking into ‘scripts’ folder of kernel sources:

from makefile.lib:

# these flags are needed for modversions and compiling, so we define them here
# $(modname_flags) defines kbuild_modname as the name of the module it will
# end up in (or would, if it gets compiled in)
# note: files that end up in two or more modules are compiled without the
#       kbuild_modname definition. the reason is that any made-up name would
#       differ in different configs.
name-fix = $(squote)$(quote)$(subst $(comma),_,$(subst -,_,$1))$(quote)$(squote)
basename_flags = -dkbuild_basename=$(call name-fix,$(basetarget))
modname_flags  = $(if $(filter 1,$(words $(modname))),\
                 -dkbuild_modname=$(call name-fix,$(modname)))

from makefile.build:

# default for not multi-part modules
modname = $(basetarget)
$(multi-objs-m)         : modname = $(modname-multi)
$(multi-objs-m:.o=.i)   : modname = $(modname-multi)
$(multi-objs-m:.o=.s)   : modname = $(modname-multi)
$(multi-objs-m:.o=.lst) : modname = $(modname-multi)
$(multi-objs-y)         : modname = $(modname-multi)
$(multi-objs-y:.o=.i)   : modname = $(modname-multi)
$(multi-objs-y:.o=.s)   : modname = $(modname-multi)
$(multi-objs-y:.o=.lst) : modname = $(modname-multi)

from kbuild.include:

# filename of target with directory and extension stripped
basetarget = $(basename $(notdir $@))

from: makefile.lib

# finds the multi-part object the current object will be linked into
modname-multi = $(sort $(foreach m,$(multi-used),\
        $(if $(filter $(subst $(obj)/,,$*.o), $($(m:.o=-objs)) $($(m:.o=-y))),$(m:.o=))))

with all that, you can basically define kbuild_modname in ‘objects and symbols’ to be set to your module name as you define it in your makefile. things are a little bit more tricky if you have multiple modules built in a single project...

after solving that you will notice that eclipse indexer still throws out warnings at you (i assume you are building external module with module defined in ‘objects and symbols’)

• problem description: unused static function '__exittest'
• problem description: unused static function '__inittest'
• problem description: unused declaration of function 'cleanup_module'
• problem description: unused declaration of function 'init_module'

those are symbols used by kernel module loading/unloading system so eclipse can know nothing of them. unfortunately, as of today (eclipse 4.8.0 with cdt 9.5.2) i cannot configure code analysis to exclude those symbols from warnings, so have to suppress warnings putting following to the lines of code where you define module initialization:

// @suppress("unused static function") @suppress("unused function declaration")