diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2011-08-16 18:13:04 +0100 |
---|---|---|
committer | Saul Wold <sgw@linux.intel.com> | 2011-08-18 13:45:43 -0700 |
commit | 4316c5e9eec67d71f4699102a63a5f968bd8d1d9 (patch) | |
tree | ffd7526418403d68c7a3c8853cacad3dcf6a3f5d /meta/files | |
parent | 2e83e6755441cb14bd907d306974338c15173189 (diff) | |
download | openembedded-core-4316c5e9eec67d71f4699102a63a5f968bd8d1d9.tar.gz openembedded-core-4316c5e9eec67d71f4699102a63a5f968bd8d1d9.tar.bz2 openembedded-core-4316c5e9eec67d71f4699102a63a5f968bd8d1d9.tar.xz openembedded-core-4316c5e9eec67d71f4699102a63a5f968bd8d1d9.zip |
image.bbclass, kernel.bbclass: create warning file about deleting deploydir files
New users sometimes delete files in tmp/deploy/images assuming they will
be re-created just by re-running the build, and then are confused when
this doesn't work. To discourage people from doing this, create a file
called README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt in
tmp/deploy/images containing an explanation of what needs to be done to
re-create files there.
Fixes [YOCTO #1315] and [YOCTO #1346].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta/files')
-rw-r--r-- | meta/files/deploydir_readme.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/meta/files/deploydir_readme.txt b/meta/files/deploydir_readme.txt new file mode 100644 index 000000000..97ec1855f --- /dev/null +++ b/meta/files/deploydir_readme.txt @@ -0,0 +1,8 @@ +Files in the deploy directory will not be re-created automatically if you +delete them. If you do delete a file, you will need to run: + + bitbake -c clean TARGET + bitbake TARGET + +where TARGET is the name of the appropriate package or target e.g. +"virtual/kernel" for the kernel, an image, etc. |