staging/chunkeey/scripts/combined-ext-image.sh, branch master

build: introduce $(MKHASH)

2021-05-13T13:13:15Z

Before this commit, it was assumed that mkhash is in the PATH. While this was fine for the normal build workflow, this led to some issues if make TOPDIR="$(pwd)" -C "$pkgdir" compile was called manually. In most of the cases, I just saw warnings like this: make: Entering directory '/home/.../package/gluon-status-page' bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found bash: line 1: mkhash: command not found [...] While these were only warnings and the package still compiled sucessfully, I also observed that some package even fail to build because of this. After applying this commit, the variable $(MKHASH) is introduced. This variable points to $(STAGING_DIR_HOST)/bin/mkhash, which is always the correct path. Signed-off-by: Leonardo Mörlein

combined-ext-image.sh: generate image in temp dir

2018-01-13T06:58:46Z

The new build commands operate on the input image and use it again as output image. This conflicts with the way combined-ext-image.sh was operating. It required that input and output files are different files and and that it can write freely to the output file. This can be avoided when all intermediate build steps by combined-ext-image.sh are done in a temporary directory. The output file is then only overwritten in the last step. Signed-off-by: Sven Eckelmann

build: use mkhash to replace various quirky md5sum/openssl calls

2017-01-05T10:09:12Z

Signed-off-by: Felix Fietkau

scripts: add script to generate combined extended image format

2011-11-30T07:43:58Z

Signed-off-by: Marek Lindner SVN-Revision: 29358