-
Notifications
You must be signed in to change notification settings - Fork 412
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
Dune 3 dune exec --
on Windows _always_ rebuilds the executable
#5466
Comments
My two cents: artifact subtitution is not done inside _build, and not done before executing with You can perhaps test with |
So even if the targets are present on the filesystem, they're ignored. |
Oh, wow, judging by the output you get, everything gets rebuilt for you (not just the executable). Could you do the same with |
The target
|
Running |
The same problem seems to appear with |
@snowleopard any other idea? let me know if I can help. |
Sorry, I couldn't find a chance to investigate this yet. What needs to be done is debugging why Dune's workspace-local cache isn't effective in this case. The main module that is responsible for caching build rules is |
@MisterDA could you submit a cram test that reproduces this problem? That would be a good first step to address this. |
FWIW, I can't reproduce this. The second run is a clean "Hello, world" without any cache message. |
(dune 3.1.1) |
The bug is in 3.0.2 but not in 3.1.1. Not sure by what, but I think that we can close this one. |
With dune.3 on Windows, when I
dune exec --
using the executablepublic_name
, without the.exe
, the executable is always rebuild. I think that's a regression.Using the "local" name (e.g.,
./main.exe
) also forces recompilation each time.Possibly related to (but I don't think so):
@snowleopard wrote:
The text was updated successfully, but these errors were encountered: