I didn't see a single example of build script usage where it wasn't tied to the sources and where the sources could be easily compiled without it. The sources define what the binary will look like and so do the build scripts. That's why I think it's a good idea to combine them.

As for the question "where to put those comments?":
There was an enhancement issue in bugzilla about allowing modules to be named "package" in which case they are imported by their package name alone. The build comments in those modules would be propagated to the entire package and the subpackages would be able to override.


On Tue, Nov 27, 2012 at 9:40 PM, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
On 11/27/12 12:37 PM, jerro wrote:
Providing arbitrary compiler flags would already be a huge gain. So one
can pass libs, -I include paths, ...

You can already pass -I and -L and they are passed on to DMD (along with
any other flags that rdmd doesn't recognize AFAIK.

The advantage would be that you get to wire the options inside the script instead of requiring them in the invocation thereof.

Again, --shebang does help there but my experience with it has been terrible: I recall on one OS the shebang line was silently truncated so some of my options were not passed although I was convinced they were.


Andrei



--
Bye,
Gor Gyolchanyan.