Commit 24837ff4 by Ivan Efimov

Commit Title: Prepare OpenSource "meta-inango-crossreference" for push to Yocto Project

BugID: 14786
Bug Fixed(y/N[blankN]):
CodeReviewId: 4201

* conf/layer.conf:
** changed layer name: inango -> inango-crossreference
** add LAYERVERSION... = "1"
* README: removed expression which may be interpreted as intolerance for accepting community changes into project
* .gitignore: add wildcards for git and Python temporary/bkup files

Signed-off-by: Ivan Efimov <>
parent 971e5320
# Vim tmp files
# Vim swap and editors backup files
# Artifacts from git format-patch and patch utilities
# Compiled python files in case if we'll create own lib/something python code
......@@ -52,9 +52,6 @@ This layer support next cross reference tools itself:
* ctags (by default)
* cscope
If you want to add support of another tool then you may do that in your meta
Currently used tool is defined by CROSS_REFERENCE_TOOL variable.
......@@ -89,8 +86,7 @@ starts with prefix CROSS_REFERENCE_
IV. Adding the Inango layer to your build
In order to use this layer, you need to make the build system aware of
In order to use this layer, you need to make the build system aware of it.
Assuming the Inango layer exists at the top-level of your
yocto build tree, you can add it to the build system by adding the
......@@ -23,13 +23,18 @@ BBPATH .= ":${LAYERDIR}"
# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
BBFILE_PRIORITY_inango = "6"
BBFILE_COLLECTIONS += "inango-crossreference"
BBFILE_PATTERN_inango-crossreference = "^${LAYERDIR}/"
BBFILE_PRIORITY_inango-crossreference = "6"
LAYERSERIES_COMPAT_inango-crossreference = "morty thud warrior"
# This should only be incremented on significant changes that will
# cause compatibility issues with other layers
LAYERVERSION_inango-crossreference = "1"
LAYERSERIES_COMPAT_inango = "morty thud warrior"
INHERIT += "cross-reference"
IMAGE_CLASSES += "image-cross-reference"
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment