Skip to content

Commit 5bf5b95

Browse files
Release: Don't require DEPLOY_DESTINATION being an argument to make
DEPLOY_DESTINATION variables was set to empty value in release.mk, thus value set in environment was ignored - to set it user would have to either set via make command arguments or via release.config. This was inconsistent with DEPLOY_BUILD_DESTINATION, which could have been used implicitly from environment. This patch unifies behaviour for both variables. Signed-off-by: Anton Kolesov <[email protected]>
1 parent 0f9cac2 commit 5bf5b95

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

release.mk

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,6 @@
3030

3131
CONFIG_STATIC_TOOLCHAIN := n
3232

33-
DEPLOY_DESTINATION =
34-
3533
# Whether to build big endian toolchain
3634
ENABLE_BIG_ENDIAN := y
3735

0 commit comments

Comments
 (0)