allow configuring newline style for build output

[Rawld Gill]

The build system always uses "\n" for newline when generating output. This may be inconvenient for some editors in some environments. Further, since most of the dojo source contains \r\n for newlines, adding just a few single \n newlines causes the file to have mixed newline styles which further confuses some editors/IDEs. All this combines to make debugging build output painful for some dev environments.

Add a profile configuration variable that overrides the default newline sequence.

[Rawld Gill]

In [27542]:

added profile switch 'newline' which may be used to override the default newline sequence ('\n') for generated output during a build; fixes #14603; !strict

[ben hockey]

bc.newline is undefined with --check-args command line switch

[Mathevet julien]

I got also

error(324) Error while transforming resource. resource: dojo/dojo.js transform: 5; error: InternalError?: il manque ':' après un identifiant de propriété

And my dojo.js.uncompressed.js containes undefined for newline too

[ben hockey]

builds completely fail (no dojo.js) silently with this problem so escalating to a higher severity. at first i hadn't noticed this issue until i blew away my release directory and saw that there was no dojo.js

[ben hockey]

rawld, i believe the circular dependency from buildControl -> stringify -> buildControl is causing the problem. the buildControl factory is not being executed.

[Rawld Gill]

In [27575]:

fixed circular dependency in stringify; fixes #14603; !strict

[Rawld Gill]

Replying to neonstalwart:

rawld, i believe the circular dependency from buildControl -> stringify -> buildControl is causing the problem. the buildControl factory is not being executed.

Thanks Ben! That seemed to be it re the check-args.

I don't understand why dojo.js wasn't building...that was working on my machine. Maybe I've got a local condition that causes that error to not be seen. Let me know if you see further problems.