You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Target checks via: if [ -x $(CONFIGURE_CMD) ]; then
yet host does: if [ -x configure ]; then
So trying to use this, will fail for the target, but not for the host.
CONFIGURE_CMD = ./buildtools/bin/waf configure
HOST_CONFIGURE_CMD = ./buildtools/bin/waf configure
This results in ./buildtools/bin/waf: binary operator expected for the target.
The check is flawed in both cases, the host does not check for the custom configure command and the target is doing a file check only, so you have to ensure the actual "configure" argument is first in the CONFIGURE_ARGS. CONFIGURE_ARGS:=configure $(CONFIGURE_ARGS)
This is confusing and both cases should work similar and check for CONFIGURE_CMD and maybe we should add a CONFIGURE_CMD_ARGS variable, that can hold custom arguments.
The text was updated successfully, but these errors were encountered:
Andy2244:
Target checks via:
if [ -x $(CONFIGURE_CMD) ]; then
yet host does:
if [ -x configure ]; then
So trying to use this, will fail for the target, but not for the host.
CONFIGURE_CMD = ./buildtools/bin/waf configure
HOST_CONFIGURE_CMD = ./buildtools/bin/waf configure
This results in
./buildtools/bin/waf: binary operator expected
for the target.The check is flawed in both cases, the host does not check for the custom configure command and the target is doing a file check only, so you have to ensure the actual "configure" argument is first in the CONFIGURE_ARGS.
CONFIGURE_ARGS:=configure $(CONFIGURE_ARGS)
This is confusing and both cases should work similar and check for CONFIGURE_CMD and maybe we should add a CONFIGURE_CMD_ARGS variable, that can hold custom arguments.
The text was updated successfully, but these errors were encountered: