-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
sourcePaths
does not work as documented with configurations
#1913
Comments
sourcePaths
does not work as documentedsourcePaths
does not work as documented with configurations
That sentence really is fuzzy. So the current behavior is "... no |
That's the behavior I was expecting. For reference, my use case is a main executable, and a few small tools next to it. I could use subpackages for that but I'm really note fan of Vibe.d's |
Coding which causes current behavior be found here Line 674 in a12c19f
|
`sourcePaths` is only default initialized when both top level and configuration level `sourcePaths` is empty. Fixes dlang#1913
`sourcePaths` is only default initialized when both top level and configuration level `sourcePaths` is empty. Fixes dlang#1913
`sourcePaths` is only default initialized when both top level and configuration level `sourcePaths` is empty. Fixes dlang#1913
`sourcePaths` is only default initialized when both top level and configuration level `sourcePaths` is empty. Fixes dlang#1913
There's a workaround which I just tried that seemed to work: don't name the top-level directory |
System information
dub.json edited to:
Result:
However, according to the documentation:
Emphasis mine. This only works if
sourcePaths
is at the top level:Compiles successfully.
The text was updated successfully, but these errors were encountered: