Skip to content

new-build ignores --builddir option #4127

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

Closed
DanielG opened this issue Nov 22, 2016 · 1 comment
Closed

new-build ignores --builddir option #4127

DanielG opened this issue Nov 22, 2016 · 1 comment

Comments

@DanielG
Copy link
Collaborator

DanielG commented Nov 22, 2016

cabal new-build doesn't seem to respect --builddir, regardless of what I pass it still creates the dist-newstyle directory.

This is with HEAD (2146ea1).

As far as I can tell this is because DestDirLayout is constructed without considering any of the *DistPref fields from CliConfigFlags.

See

let distDirLayout = defaultDistDirLayout projectRootDir

I wouldn't mind submitting a PR for this if anyone can point out a good way to do this since I'm still new to the new-build code.

@ezyang
Copy link
Contributor

ezyang commented Nov 22, 2016

See also #4124

ezyang added a commit to ezyang/cabal that referenced this issue Nov 26, 2016
Previously, these flags had no affect on new-build.
Now, they let you specify where the dist-newstyle directory
should go.

Note that if a relative path is provided, it is resolved
relative to the *project root*.  If this is undesirable,
pass an absolute path instead.

Fixes haskell#4127.

Signed-off-by: Edward Z. Yang <[email protected]>
@ezyang ezyang closed this as completed in 4c7f935 Nov 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants