Leonardo Mörlein b993b68b6c build: introduce $(MKHASH)
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 <me@irrelefant.net>
2021-05-13 15:13:15 +02:00
..
2021-03-19 13:35:55 +00:00
2019-11-14 22:53:31 +01:00
2018-02-11 14:39:16 +01:00
2021-03-17 08:42:05 +01:00
2021-03-15 00:48:42 +00:00
2021-05-13 15:13:15 +02:00
2021-05-10 10:57:09 +01:00
2020-10-25 12:36:22 +00:00
2020-05-24 17:01:36 +02:00
2021-04-14 08:33:12 +02:00
2020-05-23 13:38:12 +02:00