currently refactoring a pile of (closely-related) board support code and can clearly stuff a lot of duplicate code and header files into a vendor-specific "common/" directory so just want to make sure i'm doing this properly.
first, i can see from the top-level Makefile that a common board directory is identified specifically by containing a Makefile:
HAVE_VENDOR_COMMON_LIB = $(if $(wildcard $(srctree)/board/$(VENDOR)/common/Makefile),y,n)
but not necessarily a Kconfig file.
(in fact, i can see that of the several vendors that have common/ directories, only ti/common/ has a Kconfig file, so i'm concluding that a common/ directory containing a Kconfig file is more the exception rather than the norm. ti/common/ seems like a special case, in that it contains just some board_detect code, and its Kconfig would be explicitly sourced by the subset of ti boards for which it's relevant, so that makes sense. but, as i mentioned, that's the only example i see.)
next, when including common header files, it seems clear that board files need to refer explicitly to that sibling directory, as in:
#include "../common/qixis.h"
i suppose it might have been possible for the build process to add the common directory to the include search path for header files, but it's clear that wasn't done so common header file inclusion *needs* that "../common/whatever.h" form, correct?
finally, in terms of pulling in common source files, i'm just going to be appalled by the occasional form of this:
amcc/bubinga/flash.c:#include "../common/flash.c" amcc/walnut/flash.c:#include "../common/flash.c" amcc/bamboo/flash.c:#include "../common/flash.c" amcc/luan/flash.c:#include "../common/flash.c"
or is textual inclusion of source files from a common directory acceptable practice? i normally really dislike this, but is doing that in this specific context in u-boot considered acceptable?
in any event, the regular way appears to be having a Makefile controlling what vendor-common code gets compiled, and Kconfig files elsewhere allowing the selection of config options to drive that process, is that about right?
am i missing anything regarding proper common/ vendor usage?
rday