linux/poky.git/.gitignore, branch yocto-5.0.6

vscode: drop .vscode folder

2024-02-19T11:34:33+00:00

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 Signed-off-by: Richard Purdie

vscode: add minimal configuration

2023-11-21T21:34:04+00:00

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 Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

.gitignore: ignore files generated by Toaster

2023-01-12T23:09:52+00:00

When Toaster is run as documented on https://docs.yoctoproject.org/toaster-manual/setup-and-use.html Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni

bitbake: gitignore: ignore runqueue-tests/bitbake-cookerdaemon.log

2021-03-12T16:47:12+00:00

(Bitbake rev: 2787c3dadbc94925aa1cba6c2e765ffa9f7a7c4a) Signed-off-by: Paul Gortmaker Signed-off-by: Richard Purdie

scripts/install-buildtools: improvements

2020-04-01T10:44:23+00:00

* 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/ * 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 Signed-off-by: Richard Purdie

gitignore: Ignore repo tool directory

2018-10-29T17:26:47+00:00

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 Signed-off-by: Richard Purdie

gitignore: ignore bitbake documentation build products

2018-03-28T11:50:25+00:00

Missed the bitbake manual the last time around because it's in a different directory. Signed-off-by: Sascha Silbe Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gitignore: ignore documentation build products

2018-01-06T22:40:03+00:00

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=" as well as "make DOC= pdf". While at it, make sure the patterns only match for the top-level documentation directory. Signed-off-by: Sascha Silbe Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

add !meta-poky to .gitignore file

2016-03-26T08:06:58+00:00

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 Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gitignore: fix overzealous exclusion

2015-11-16T11:39:38+00:00

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 Signed-off-by: Ross Burton Signed-off-by: Richard Purdie