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
Currently running "dub" or "dub run" will build a project in a temporary folder instead of the project folder as "dub build" does. The reason for this is to support running projects in directories where the user doesn't have write privileges and to avoid cluttering projects when they are just being run.
However, this has some drawbacks:
Windows will create a new firewall entry per "dub run" because the executable lives in a different path each time
Builds cannot be reused (currently only possible using "dub build --rdmd"
So even if the current behavior avoids cluttering the project folder by default, changing the behavior seems to be the better choice overall. If the project folder is not writable, the current behavior will stay as a fallback.
The text was updated successfully, but these errors were encountered:
Currently running "dub" or "dub run" will build a project in a temporary folder instead of the project folder as "dub build" does. The reason for this is to support running projects in directories where the user doesn't have write privileges and to avoid cluttering projects when they are just being run.
However, this has some drawbacks:
So even if the current behavior avoids cluttering the project folder by default, changing the behavior seems to be the better choice overall. If the project folder is not writable, the current behavior will stay as a fallback.
The text was updated successfully, but these errors were encountered: