Skip to content
New issue

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

Fixes behaviour of default stdlib when internal-build-flag is set #2283

Merged
merged 5 commits into from
Aug 9, 2023

Conversation

paulcadman
Copy link
Collaborator

The mechanism for using --internal-build-flag to set the build directory for the default stdlib location already existed, it was just unused (Nothing always passed in, instead of the entry point):

addDependency' = addDependencyHelper Nothing

This PR fixes that issue, adds some smoke tests to check the behaviour of the stdlib dependency.

The issue with what to do with relative stdlib dependency paths when --internal-build-flag is set remains open: #2274

@paulcadman paulcadman added this to the 0.4.3 milestone Aug 8, 2023
@paulcadman paulcadman self-assigned this Aug 8, 2023
@paulcadman paulcadman requested a review from jonaprieto August 8, 2023 17:55
@jonaprieto jonaprieto force-pushed the bug-internal-build-dir-compile branch from d3997b1 to 8f3e134 Compare August 9, 2023 14:22
@paulcadman paulcadman merged commit 7b000eb into main Aug 9, 2023
@paulcadman paulcadman deleted the bug-internal-build-dir-compile branch August 9, 2023 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

internal-build-dir flag is not respected when default stdlib is used
2 participants