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
{{ message }}
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
I would like to make a change to the resolveCommands() function in zopen-build and I'm seeking some feedback. Currently this function checks for the existence of the command (like command -V ./configure) before it sets the appropriate envar. Unfortunately at this point sometimes the commands don't exist yet! For example in the expat build configure is created only after the bootstrap phase. This currently causes the configure step to be skipped because zopen thinks the configure command doesn't exist. I would like to remove the command -V check altogether. Thoughts?
The text was updated successfully, but these errors were encountered:
Also, I would like to avoid moving the code for resolveCommands() to later because it is convenient to have the commands at your fingertips when the zopen build --shell options is used.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to make a change to the resolveCommands() function in zopen-build and I'm seeking some feedback. Currently this function checks for the existence of the command (like command -V ./configure) before it sets the appropriate envar. Unfortunately at this point sometimes the commands don't exist yet! For example in the expat build configure is created only after the bootstrap phase. This currently causes the configure step to be skipped because zopen thinks the configure command doesn't exist. I would like to remove the command -V check altogether. Thoughts?
The text was updated successfully, but these errors were encountered: