Windows Executables about spec HOT 6 CLOSED

Combining this with the suggestion in the working doc, how about (for each /bin/*):
POSIX: /bin/build, /bin/build.sh
Windows: /bin/build.exe, /bin/build.ps1, /bin/build.bat, /bin/build.cmd

We also need to define the equivalent env vars that should be constructed for each layer. For example, what's the equivalent of LD_LIBRARY_PATH or C_INCLUDE_PATH on Windows?

The lifecycle builder is nearly cross-platform already, so once we answer those questions, we just need:

1. Windows values for these,
2. The executable order changes mentioned above, and
3. A launcher implementation for Windows (similar to this)

from spec.

/cc @ivo4311

from spec.

Probably want to specify that EXACTLY one of each can be present, otherwise behavior is undefined.

from spec.

I believe that windows does that expansion anyway, if I am correct we could decide to not specify and let windows convert detect to detect.exe (or others)

from spec.

@nebhale I believe this will be addressed by #62

from spec.

Superseded by #62.

from spec.