Below is the current status of EBuild, as of August 21, 2018. Feedback and bug reports on EBuild are very much appreciated (ideally here on Talk), but keep the status in mind for what you expect to work and what not. Source access via GitHub is available upon request.
- Fire: EBuild is the default tool chain for all projects.
- Water: EBuild is the default tool chain for all projects.
- Visual Studio: EBuild is the default tool chain for all except UWP, WinRT and Classic ASP.NET Echoes projects.
Compile plain projects (.exe, .dll)
- .NET Framework (full), including WinForms and WPF
- .NET Standard
- .NET Core
- ASP..NET Core
- Resolving NuGet package references internally
Secondary build tasks:
Does not work yet:
- Resource .dlls
Advanced tool chain support for:
- Universal Windows Platform
- Classic ASP.NET (mostly deprecated)
- WinRT (deprecated)
- Windows Phone Platform (deprecated)
- Silverlight (deprecated)
EBuild is now the default tool chain for all Echoes projects except UWP, Classic ASP.NET and the deprecated WinRT, Windows and Silverlight.
Fully functional, EBuild is now the only supported build chain for Cooper, and all Java and Android projects will always build with EBuild.
Fully functional. EBuild is now the only supported build chain for Cocoa, and all macOS, iOS, tvOS and watchOS projects will always build with EBuild.
Fully functional, EBuild is now the only supported build chain for Island, and all Island projects will always build with EBuild.
Mixed (Mixed-platform Projects)
Projects with multiple targets are fully supported and functional in EBuild, and partially supported in the Fire and Water IDE (targets will show details, but cannot be added or edited yet, except by manually tweaking the project file XML). Mixed/multi-target projects are not and will not be supported in Visual Studio.
Gotham (Cross-platform Libraries)
Compiler support for Gotham is in progress and not publicly available yet.