All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Coolidge <ian@boundarydevices.com>
To: meta-freescale@yoctoproject.org
Subject: [meta-fsl-arm-extra][PATCH] u-boot-script-boundary: Fix paths for bootscript and upgrade script
Date: Tue, 19 Jul 2016 18:28:46 -0700	[thread overview]
Message-ID: <1468978126-16408-1-git-send-email-ian@boundarydevices.com> (raw)

Signed-off-by: Ian Coolidge <ian@boundarydevices.com>
---
 recipes-bsp/u-boot/u-boot-script-boundary_git.bb | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
index 3ad140b..ffe124e 100644
--- a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
+++ b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
@@ -18,17 +18,17 @@ UPGRADESCRIPT = "${S}/board/boundary/nitrogen6x/6x_upgrade.txt"
 
 do_mkimage () {
     # allow deploy to use the ${MACHINE} name to simplify things
-    if [ ! -d board/boundary/${MACHINE} ]; then
-        mkdir board/boundary/${MACHINE}
+    if [ ! -d ${S}/board/boundary/${MACHINE} ]; then
+        mkdir ${S}/board/boundary/${MACHINE}
     fi
 
     uboot-mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
                   -n "boot script" -d ${BOOTSCRIPT} \
-                  board/boundary/${MACHINE}/6x_bootscript
+                  ${S}/board/boundary/${MACHINE}/6x_bootscript
 
     uboot-mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
                   -n "upgrade script" -d ${UPGRADESCRIPT} \
-                  board/boundary/${MACHINE}/6x_upgrade
+                  ${S}/board/boundary/${MACHINE}/6x_upgrade
 }
 
 addtask mkimage after do_compile before do_install
-- 
1.9.1



                 reply	other threads:[~2016-07-20  1:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1468978126-16408-1-git-send-email-ian@boundarydevices.com \
    --to=ian@boundarydevices.com \
    --cc=meta-freescale@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.