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

Cabal library implicitly depends upon global current working directory #3051

Closed
bgamari opened this issue Jan 15, 2016 · 2 comments
Closed

Comments

@bgamari
Copy link
Contributor

bgamari commented Jan 15, 2016

The Cabal library (in particular configure) appears to depend implicitly upon the process's current working directory, making it rather tricky to use in a larger application. See, for instance, snowleopard/hadrian#170.

@BardurArantsson
Copy link
Collaborator

If I recall correctly during my work on trying to search for the .cabal file in parent directories, this is actually surprisingly non-trivial to do.

(Not that I wouldn't like to see it, but I'm just leaving this note in case anyone wants to attempt it.)

@quasicomputational
Copy link
Contributor

AIUI, @angerman has solved this with #4874, and, while there are probably still lurking bugs and definitely some spots of CWD dependence, this is done well enough that Hadrian's happy with it.

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

4 participants