Add support for producing ecma compliant "exe" #2754
Comments
- Exe in this sense doesn't make the output file an exe, it's about being able to create things that have an ECMA compliant entrypoint. This will allow us to use dnu to build the mono host. #2754
- Exe in this sense doesn't make the output file an exe, it's about being able to create things that have an ECMA compliant entrypoint. This will allow us to use dnu to build the mono host. #2754
|
I presume this fixes #1997 as well? |
|
With this option, a compiler will still have to use the ".dll" extension when ordered to spit out files to disk? |
|
@akoeplinger Hah, didn't even see that. |
|
@bojanrajkovic You can do what you want to really. We're not changing the .dll extension. |
|
Makes me wonder if we should call it emitEntryPoint so we don't confuse people when the output isn't an exe. |
- It will remove the confusion about not actually outputting a .exe #2754
|
Done, the compiler option is emitEntryPoint |
|
Great 👏 |
|
@davidfowl Heh, I think you meant @borgdylan. Was wondering what I'd gotten myself into this time. |
|
Oops! 😀 |
|
@davidfowl I thought the answer was not meant for me. Thanks for clearing this. Now I can implement the right behaviour in my provider. |
|
Will it ever be possible for DNX to produce a native binary for a target platform (replaces dnx.exe) as a static app-specific bootstrapper (would contain managed .dll program nearby or within it, or could be completely native if NGEN'd)? I think that would be pretty cool. |
|
I found it easy to implement this for my own language support. Would this have any application apart from writing DNX hosts or command line tools to have no dependencies that are external to the BCL? |
This will allow us to use dnx to produce the host as well.
https://github.com/aspnet/dnx/blob/dev/src/Microsoft.Dnx.Host.Mono/EntryPoint.cs
The text was updated successfully, but these errors were encountered: