From: Trevor Woerner <twoerner@gmail.com>
To: Eddie Cai <eddie.cai.linux@gmail.com>
Cc: yocto@yoctoproject.org, Jacob Chen <jacob-chen@iotwrt.com>
Subject: Re: [meta-rockchip][PATCH v4] classes: rockchip-gpt-img: add
Date: Mon, 27 Feb 2017 22:08:14 -0500 [thread overview]
Message-ID: <20170228030814.GA8559@linux-uys3> (raw)
In-Reply-To: <CAJrj+DPQFRDxsF=2=T6sfdfhiHvHD6n0KbH6jS0nJfLjA2NxPA@mail.gmail.com>
Hi Eddie,
On Tue 2017-02-28 @ 08:48:16 AM, Eddie Cai wrote:
> Could you also copy ${BOOT_IMG} to ${DEPLOY_DIR_IMAGE} . That is much
> earier for people find boot image. In case they want to flash boot
> partition alone.
All of this work is always done in DEPLOY_DIR_IMAGE.
$ bitbake core-image-minimal -e | grep "^DEPLOY_DIR_IMAGE="
DEPLOY_DIR_IMAGE="/z/rockchip/master/build/tmp-glibc/deploy/images/firefly-rk3288"
$ bitbake core-image-minimal -e | grep "^BOOT_IMG="
BOOT_IMG="boot.img"
With this class file as submitted in v4, if I build my first image I get:
$ ls -lh tmp-glibc/deploy/images/firefly-rk3288/
-rw-r--r-- 1 trevor users 137M Feb 27 14:05 core-image-minimal-firefly-rk3288-20170227190504.gpt-img
lrwxrwxrwx 1 trevor users 56 Feb 27 14:06 core-image-minimal-firefly-rk3288.gpt-img -> core-image-minimal-firefly-rk3288-20170227190504.gpt-img
If I adjust the image then build it again I get:
$ ls -lh tmp-glibc/deploy/images/firefly-rk3288/
-rw-r--r-- 1 trevor users 137M Feb 27 14:05 core-image-minimal-firefly-rk3288-20170227190504.gpt-img
-rw-r--r-- 1 trevor users 137M Feb 27 14:06 core-image-minimal-firefly-rk3288-20170227190628.gpt-img
lrwxrwxrwx 1 trevor users 56 Feb 27 14:06 core-image-minimal-firefly-rk3288.gpt-img -> core-image-minimal-firefly-rk3288-20170227190628.gpt-img
As you can see:
- the images appear in DEPLOY_DIR_IMAGE
- the first gpt-img is still there
- after each build the "core-image-minimal-firefly-rk3288.gpt-img" symlink
always points to the latest gpt-img file
Is this what you were hoping for?
next prev parent reply other threads:[~2017-02-28 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:20 [meta-rockchip][PATCH v4 0/1] classes: rockchip-gpt-img: add Trevor Woerner
2017-02-27 19:20 ` [meta-rockchip][PATCH v4] " Trevor Woerner
2017-02-28 0:48 ` Eddie Cai
2017-02-28 3:08 ` Trevor Woerner [this message]
2017-02-28 4:42 ` Eddie Cai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170228030814.GA8559@linux-uys3 \
--to=twoerner@gmail.com \
--cc=eddie.cai.linux@gmail.com \
--cc=jacob-chen@iotwrt.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.