-
Notifications
You must be signed in to change notification settings - Fork 704
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
new-run not running the executable #4477
Comments
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Looking at CmdRun.hs it looks like it's just not implemented. CC @dcoutts. |
No, it's not so easy to fix. From @dcoutts:
|
Completed the 'new-run' command (#4477). The functionality is the same of the old 'run' command but using nix-style builds. Additionally, it can run executables across packages in a project.
This isn't working for me using cabal-install 2.0.0.1. Versions:
Steps to reproduce: Create new executable project,
Let me know if there's any other information you need, thanks! |
I'm testing with the
2.0
branch. My package built successfully and has one executable section. Thenew-run
command correctly checks if things are up to date and rebuilds them, but it is not running the executable. I added printouts inmain
that I never see and the program should block on agetContents
but it doesn't do that either. I've tried addingexe:mypkg
to thenew-run
command and it doesn't change the behavior.@dmwit
The text was updated successfully, but these errors were encountered: