We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compare the later entries in both sections; they're nigh-identical. First set of calls: as a child script, from the top-level build.sh. Second set: as a dependency, from web/src/test/manual, which does not include web/src/tools as a viable child-project folder.
Compare the later entries in both sections; they're nigh-identical.
First set of calls: as a child script, from the top-level build.sh.
Second set: as a dependency, from web/src/test/manual, which does not include web/src/tools as a viable child-project folder.
web/src/test/manual
web/src/tools
I reckon we should consider tweaking builder.inc.sh to handle the scenario of child vs dependency calls resulting in multiple calls.
Originally posted by @mcdurdin in #9743 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I reckon we should consider tweaking builder.inc.sh to handle the scenario of child vs dependency calls resulting in multiple calls.
Originally posted by @mcdurdin in #9743 (comment)
The text was updated successfully, but these errors were encountered: