On 01/20/2015 01:37 AM, Kévin THIERRY wrote:
On Tue, Jan 20, 2015 at 9:28 AM, 정대순 <[email protected]> wrote:
Dear THIERRY,
I have two questions.
1. After build, if I want to new build, how to clean?
I try following commands, but do not clean.
$bitbake -c clean tizen-common-core-image-crosswalk-dev
or
$bitbake -b tizen-common-core-image-crosswalk-dev.bb -c clean
No need to use the -b option that not needed unless you are working on a
recipe that is not in the common BBPATH (as defined in bblayers.conf)
or
$bitbake -c cleanall tizen-common-core-image-crosswalk-dev
"cleanall" removes everything (source, cache, build dir, RPM...) linked to
the package(s)/package-group/image put in parameter whereas clean doesn't.
I don't remember exactly what "clean" doesn't remove but you should be able
to find it in the Yocto documentation.
There are 3 variations of clean'ing, these are all defined in the
documentation (see
http://www.yoctoproject.org/docs/1.7.1/mega-manual/mega-manual.html#ref-tasks-clean)
1) bitbake -c clean <target>
This will remove the workdir and any artifacts installed into the sysroot.
2) bitbake -c cleansstate <target>
This will remove the above along with the shared state files.
3) bitbake -c cleanall <target>
As Kevin states below, will remove everything above (workdir, sysroot
artifacts, shared state files) along with the downloaded source tarball
or Source Code Management files (git, svn, ...)
This should only be used in extreme conditions.
Note that "cleanall" on an image doesn't remove the source of the packages
thet are part of the image.
The best way to clean everything to start from scratch is to delete
everything in your build directory except the conf/ directory (and maybe
the downloads directory if it is located there and you don't want to fetch
all the sources again).
I would not recommend removing the "build" ($BUILDDIR) or tmp directory,
as you might delete the downloads (which could be shared among multiple
users via DLDIR.
2. When build break occur during build, if run 'bitbake
tizen-common-core-image-crosswalk-dev' again, continue build from fail task.
Just to be clear any of the clean tasks listed above will clean only the
target recipe not others. So cleaning an image will just clean up the
image workdir, not any other failed tasks that occurred before that.
Is it right? What's the difference between '--continue' option and without
option?
I don't know about the "--continue" option, I've never used it. Maybe you
can find some information about that in the Yocto documentation otherwise
you can ask this question on the Yocto mailing list.
What is the error you encounter ?
Yea, any additional information could be helpful.
Thanks
Sau!
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
