CoreRT NuGet Toolchain Packaging

[joshfree]

• [ ] initial product packaging to bring up testing and other dependencies
• [ ] Fixing library configurations to have the correct runtime assets under correct RID paths
• [ ] updating build to publish to (and pull from) myget.org

[Petermarcu]

Is netcoreapp1.0aot a tfm?

[SedarG]

initial product packaging to bring up testing and other dependencies

We are already producing the packages at bin\Product[TargetOS].[TargetArch].[Configuration]\packaging this myget feed contains CoreRT packages, though the latest one is from Feb. '16.

[SedarG]

We are already producing the packages at ...

We need to update how we build packages. Currently it's quite a hacky way: We’re building all the binaries – platform specific and agnostic – on each platform. And each platform has a runtime.json that declares the package identities and versions in the package graph, enumerating all the platform specific runtime packages. However, on say Ubuntu, we only produce Ubuntu runtime package and not OSX nor windows. That works OK in testing because we’re going to restore that package only for Ubuntu RID. This is certainly not the correct way to produce and publish packages. As far as I can see, we need to

• [ ] Define correct layering of the packages
• [ ] Define correct build behavior for all the platforms
• [ ] Upgrade the build scripts; split build to build-managed and build-native (bad naming, BTW. It should have been build-platformAgnostic, build-platformSpecific), split running tests as a separate step, after all the builds are finished. (I stroked out the other option in my previous email below)
• [ ] We need to work on build definitions and coordinate all the builds, windows, Ubuntu, OSX, etc, so that we could create the packages properly. i.e. The tests will run after On CoreFX and CoreCLR it’s done by pipeline build. We don’t have it set-up on CoreRT.
• [ ] We also need to preserve ability to build all the binaries on a single platform. It'd be bad to ask a dev to build the product on two platforms and jam them together to be able to test a change.