Build on windows needs work - tracker bug.

I’ve been trying to get the build to run on windows. The package.json build commands that assume Posix shell behaviour aren’t working out - it appears that even when npm is run from a Posix shell, the commands get run on the default shell (which looks to be cmd.exe). Its possible to work around this with `“bash -c "{blah command here}"” for every command that requires proper shell behaviour (as opposed to those that just execute some command without using command substitution, fancy redirects…). Its ugly, but its only about 16 commands.

After that, the closure compiler step dies with duplicate input files. Still tracking down why that happens - probably something in the way we build .build\gcc-java-args.

[wallw-teal]

See the completed Windows docs here

[wallw-teal]

In order to do this we’ll have to find node packages to replace:

• perl - used for search/replace, should be a simple replacement
• grep - not only is this used once in package.json, but it is also a dependency of the simple-grep node package used in opensphere-build-resolver
• cp - we initially tried a couple of different node packages for this only to be frustrated that they didn’t work as well as cp
• find - should be an easy replace, we just didn’t bother because we’d already given up on replacements for cp and grep at the time
• xargs - should be easy enough to replace or write a quick node script to process those files

And we would need to do a quick look over opensphere-build-resolver and opensphere-build-index to ensure that they are not depending on node wrappers for those native packages.