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
What is the rationale behind forbidding relative paths in the stack.yaml for extra-lib-dirs?
I often need to add a path to a local C lib, and that's not convenient to have to build it via: stack build --extra-lib-dirs $PWD/my/path
The text was updated successfully, but these errors were encountered:
Right, that probably wasn't a good idea. I think it would be nice to have something stronger than a FilePath in the option parser, and working with Path Abs Dir internally is also desirable, but of course that shouldn't come at the cost of user convenience.
This was a bit tricky, because we want these paths to be relative to the config file. Similarly, for CLI args it is relative to current work dir. Now that this info is plumbed through, it will be straightforward to add support for relative paths elsewhere in configuration.
What is the rationale behind forbidding relative paths in the stack.yaml for
extra-lib-dirs
?I often need to add a path to a local C lib, and that's not convenient to have to build it via:
stack build --extra-lib-dirs $PWD/my/path
The text was updated successfully, but these errors were encountered: