There is a new official bitbake plugin:
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
This plugin automatically updates the .vscode/settings.json file.
Having the settings.json file in git and a plugin which modifies this
file is not ideal. It can lead to anoying situations especially when
working with git. For example a git stash reverts the settings which are
automatically applied by the plugin. While git stashed the settings.json
file the plugin immediately changes the file again and tries to run
bitbake based on the newly generated settings. When git does a stash pop
the restored settings.json file conflicts with the new settigns.json
file which has been generated while the git stash took place.
Therefore this patch removes the .vscode folder from git.
Removing the settings.json leads to other issues as already described
in the commit message of 5ff688fe29. But we still need another solution
where the settings.json file is not in Git.
Discussion is here:
https://github.com/yoctoproject/vscode-bitbake/issues/95
(From OE-Core rev: f36771e155b9e0cf24a885bf3340d59036aa42c5)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is essential to configure VSCode indexer plugins to ignore the build
folder of bitbake. Otherwise, the indexer plugins run with 100% CPU load
until an OOM exception occurs. In practice, this makes VSCode more or
less unusable for working with Yocto until a file like the one added by
this commit is deployed before VSCode starts. From the user's point of
view, it is not obvious why the system runs at 100% CPU load and
eventually crashes.
It is even more misleading that VSCode starts the indexers immediately,
but does not stop or reconfigure them when the ignore list is updated.
In practice, this means that every time the ignore list is changed,
VSCode immediately starts indexing the build folder until the OOM
exception stops it. Depending on the system's OOM handler, the entire
build machine may crash.
Particularly annoying is the Python plugin that ignores the general
ignore list and requires an extra ignore section.
The settings are suitable for workflows like bitbake, devtool modify,
devtool reset. The settings are not intended to work on the source code
of a recipe. It is assumed that a separate instance of VSCode is used
per workspace folder. These per workspace instances can have different
settings depending on the details of the sources that come with the
recipe.
VSCode can change the contents of the .vscode folder, which often leads
to a dirty git status. Normally, these changes are not added to git.
Otherwise, -f can be used to add them explicitly. It is not perfect if
the folder is listed in .gitignore. But it is also not better if it is
not.
(From OE-Core rev: 52cff14a73c9f286da4f627dc1aabf5c80aee63d)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Install directory defaults to scripts/../buildtools
e.g. --directory is set by default
This avoids the user having to type in their sudo password
to install in /opt/poky/<installer-version>
* Use "." rather than "source" for sourcing the environment script
as not all distros (e.g. Debian) have "source" by default.
* Add buildtools/ to .gitignore
* Fix typos in example usage (--install-version -> --installer-version)
[YOCTO #13832]
(From OE-Core rev: c6c3a58dbf0ca6c4a41df7ff50fa56d39d7ee23f)
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reduces the noise produced by 'git status' and 'repo status' when
orchestrating the layers with Google's repo tool
(https://gerrit.googlesource.com/git-repo/).
(From OE-Core rev: 0c2c8d9edcba148c5beb22a9fb8ff06e1ada30cd)
Signed-off-by: Christian Meusel <christian.meusel@posteo.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Missed the bitbake manual the last time around because it's in a
different directory.
Signed-off-by: Sascha Silbe <x-yo17@se-silbe.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are several different manuals by now, all of which produce
output. The "eclipse" directory might even have been present the last
time .gitignore was updated.
Ignore the files and directories that can be generated during "make
DOC=<directory>" as well as "make DOC=<directory> pdf". While at it,
make sure the patterns only match for the top-level documentation
directory.
Signed-off-by: Sascha Silbe <x-yo17@se-silbe.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Another meta-yocto -> meta-poky transition item. Git complained
on commit that files in meta-poky could not be committed.
Signed-off-by: Bill Randle <william.c.randle@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was excluding any subdirectory anywhere in the tree named build*,
rather than just at the root - thus anything in
meta/recipes-devtools/build-compare had to be forcibly added. Change the
line so that it only operates at the root of the repo.
(From OE-Core rev: 3a60e5dba0ea914b1bd7a2073c1977e1d8529541)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gitignore the cache directory created by the http client
the log file for tests is already set up as an absolute path,
so no need to recompute the path
(Bitbake rev: 80f525e5cbe83e0407ecddf84401d68213c6d5cf)
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* We don't want to ignore changes in the meta-selftest directory
* While I'm at it, meta-hob has been gone for a while now, so drop the
reference to it here.
(From OE-Core rev: 6bcc652f5168d87e76b059f9e9825b8bcf049b90)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a few more files to gitignore file to allow document
generation testing.
(Bitbake rev: f6310ca9ccb402a7569a79a4e92751c6d5733697)
Signed-off-by: Bill Traynor <wmat@alphatroop.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
else for example meta-toolchain-qte.bb is also ignored.
(From OE-Core rev: d15d42562dff08696015f4d15e3e15c70ee2357a)
Signed-off-by: Eric Bénard <eric@eukrea.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Previously parts of build*/ were ignored, but unless you committed the top-level
build/ in a branch this didn't achieve anything. Change that to ignore all
top-level build* directories.
(From OE-Core rev: 6e3353872d377dfe2689832b3f04f18c2366bc8c)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support the basic workflow of trivial patches:
git format-patch HEAD~.. ; git send-email --to foo@bar.com 0001-foo.patch
We don't want git status reporting on patches lying in the top
level dir in this case.
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: f9c2d97d549e848127b741b967d90288c60f4d43)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
External distributions based on the oe-core will typically include
bitbake in the top level directory. The idea is to make it easy
for external distributions to easily assemble a distribution
with a pristine version of oe-core, add avoid the git untracked messages:
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# bitbake/
[RP: remove leading slash]
(From OE-Core rev: 9cd30beba77497288eeb2545920bc23f2a77cf16)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bitbake generates pyshtables.py to bitbake/lib/bb/pysh/ folder if the user
has write permissions there. Let's ignore generated file also on that location.
(From OE-Core rev: 975e93fadfc90b7dbdf42fa6ceaef5c38166f2d9)
Signed-off-by: Lauri Hintsala <lauri.hintsala@bluegiga.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta-XYZ directories have been manually added in the past, instead
always ignore them unless they are explicitly added
(From OE-Core rev: 3c6e85c653ce176fd2cb5a570e63c8e5da5a4e48)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ignore not just build/* but any build*/* cases.
(From OE-Core rev: 36d0edd2f4c27b4c1040ba9d9ae52eee634cc95c)
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
