On 8/8/19 1:42 PM, Richard Purdie wrote:
On Thu, 2019-08-08 at 05:55 -0700, Jason Wessel wrote:
When using a .wks.in file, the only place that the generated .wks file
exists in the tmp/work area. A copy should be left behind in the
deploy directory so that you can easily run the wic tool to
On Thu, 2019-08-08 at 05:55 -0700, Jason Wessel wrote:
> When using a .wks.in file, the only place that the generated .wks file
> exists in the tmp/work area. A copy should be left behind in the
> deploy directory so that you can easily run the wic tool to
> re-generate or modify a new image
On 8/8/19 7:55 AM, Jason Wessel wrote:
When using a .wks.in file, the only place that the generated .wks file
exists in the tmp/work area. A copy should be left behind in the
deploy directory so that you can easily run the wic tool to
re-generate or modify a new image without running bitbake.
When using a .wks.in file, the only place that the generated .wks file
exists in the tmp/work area. A copy should be left behind in the
deploy directory so that you can easily run the wic tool to
re-generate or modify a new image without running bitbake. Custom
.wks.in files can reference any
