All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
	Ryan Eatmon <reatmon@ti.com>,
	meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH 4/8] ti-rtos-firmware: Do not break the source directory by renaming files
Date: Fri, 10 Feb 2023 16:07:40 -0500	[thread overview]
Message-ID: <20230210210740.GD22689@denix.org> (raw)
In-Reply-To: <20230207234239.30720-4-afd@ti.com>

On Tue, Feb 07, 2023 at 05:42:35PM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> If we rename files in the source directory the next time we need to rebuild
> the original files will be gone and build will fail. Use symlinks instead.

Just a question - will the install/deploy steps later dereference that symlink 
and install the file content or just a now broken symlink? Would a hardlink be 
better here and avoid uncertainty/confusion?


> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
>  .../recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb       | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> index c09f67b5..3c372b32 100644
> --- a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> +++ b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> @@ -125,18 +125,18 @@ do_install:prepend:j721s2-hs-evm() {
>  # Update the am64xx ipc binaries to be consistent with other platforms
>  do_install:prepend:am64xx() {
>          ( cd ${RTOS_IPC_FW_DIR}; \
> -                mv am64-main-r5f0_0-fw ipc_echo_test_mcu1_0_release_strip.xer5f; \
> -                mv am64-main-r5f0_1-fw ipc_echo_test_mcu1_1_release_strip.xer5f; \
> -                mv am64-main-r5f1_0-fw ipc_echo_test_mcu2_0_release_strip.xer5f; \
> -                mv am64-main-r5f1_1-fw ipc_echo_test_mcu2_1_release_strip.xer5f; \
> -                mv am64-mcu-m4f0_0-fw ipc_echo_test_mcu3_0_release_strip.xer5f; \
> +                ln -s am64-main-r5f0_0-fw ipc_echo_test_mcu1_0_release_strip.xer5f; \
> +                ln -s am64-main-r5f0_1-fw ipc_echo_test_mcu1_1_release_strip.xer5f; \
> +                ln -s am64-main-r5f1_0-fw ipc_echo_test_mcu2_0_release_strip.xer5f; \
> +                ln -s am64-main-r5f1_1-fw ipc_echo_test_mcu2_1_release_strip.xer5f; \
> +                ln -s am64-mcu-m4f0_0-fw ipc_echo_test_mcu3_0_release_strip.xer5f; \
>          )
>  }
>  
>  # Update the am62xx ipc binaries to be consistent with other platforms
>  do_install:prepend:am62xx() {
>          ( cd ${RTOS_IPC_FW_DIR}; \
> -                mv am62-mcu-m4f0_0-fw ipc_echo_test_mcu2_0_release_strip.xer5f; \
> +                ln -s am62-mcu-m4f0_0-fw ipc_echo_test_mcu2_0_release_strip.xer5f; \
>          )
>  }
>  
> -- 
> 2.39.1
> 


  reply	other threads:[~2023-02-10 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 23:42 [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 2/8] ti-rtos-firmware: Remove unneeded per-machine TARGET defines Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 3/8] ti-rtos-firmware: Fix name for AM64x and AM62x firmware Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 4/8] ti-rtos-firmware: Do not break the source directory by renaming files Andrew Davis
2023-02-10 21:07   ` Denys Dmytriyenko [this message]
2023-02-10 21:14     ` Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 5/8] ti-rtos-firmware: Use defines to set firmware names Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 6/8] ti-rtos-firmware: Use a table instead of a list of copy commands Andrew Davis
2023-02-09 13:29   ` Ryan Eatmon
2023-02-09 18:11     ` Andrew Davis
2023-02-10  1:46       ` Ryan Eatmon
2023-02-10 21:23     ` Denys Dmytriyenko
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 7/8] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 8/8] ti-rtos-firmware: Deploy secure firmware unconditionally Andrew Davis
2023-02-10 21:02 ` [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Denys Dmytriyenko
2023-02-10 21:13   ` Andrew Davis
2023-02-10 21:50     ` Denys Dmytriyenko
2023-02-14  9:45       ` Jose Quaresma

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=20230210210740.GD22689@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    /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.