aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMathias Kresin <dev@kresin.me>2017-02-04 11:02:36 +0100
committerMathias Kresin <dev@kresin.me>2017-02-04 12:54:40 +0100
commit3f9a194e04a7bd857bcdd06e44616abef5dab209 (patch)
treefaed8a067afba83f2bcfe6a48b0a7f23214005a1
parentc53bb974b291fbf21c1205e777614968f0c2d767 (diff)
downloadupstream-3f9a194e04a7bd857bcdd06e44616abef5dab209.tar.gz
upstream-3f9a194e04a7bd857bcdd06e44616abef5dab209.tar.bz2
upstream-3f9a194e04a7bd857bcdd06e44616abef5dab209.zip
ramips: fix Airlink AR725W factory image build
The factory image can't be bigger than 3328 KByte. If the image is bigger than that, the gemtek-header tool throws an error and breaks the build. Make sure the output file to which the gemtek header should be added exists and wasn't removed during the check-size step because of it size. This will prevent hard errors in case the factory image is to big similar to what is done for sysupgrade images. Signed-off-by: Mathias Kresin <dev@kresin.me>
-rw-r--r--target/linux/ramips/image/rt288x.mk7
1 files changed, 5 insertions, 2 deletions
diff --git a/target/linux/ramips/image/rt288x.mk b/target/linux/ramips/image/rt288x.mk
index 3312d0ed17..f22182fbf2 100644
--- a/target/linux/ramips/image/rt288x.mk
+++ b/target/linux/ramips/image/rt288x.mk
@@ -3,7 +3,10 @@
#
define Build/gemtek-header
- mkheader_gemtek $@ $@.new $(1) && mv $@.new $@
+ if [ -f $@ ]; then \
+ mkheader_gemtek $@ $@.new $(1) && \
+ mv $@.new $@; \
+ fi
endef
define Device/ar670w
@@ -22,7 +25,7 @@ define Device/ar725w
DTS := AR725W
DEVICE_TITLE := Gemtek AR725W
IMAGES += factory.bin
- IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
+ IMAGE/factory.bin := $$(sysupgrade_bin) | check-size 3328k | \
gemtek-header ar725w
endef
TARGET_DEVICES += ar725w