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

Let "dub run" build a project in its own directory if possible #82

Closed
s-ludwig opened this issue Jun 21, 2013 · 0 comments
Closed

Let "dub run" build a project in its own directory if possible #82

s-ludwig opened this issue Jun 21, 2013 · 0 comments

Comments

@s-ludwig
Copy link
Member

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.

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

1 participant