Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developers can easily build locally from source all or part of .NET 6 on Windows, Linux, and Mac #5450

Closed
Tracked by #5437
jamshedd opened this issue Oct 27, 2020 · 9 comments
Assignees
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:2 Work that is important, but not critical for the release Team:Acquisition & Deployment User Story A single user-facing feature. Can be grouped under an epic.

Comments

@jamshedd
Copy link
Member

No description provided.

@jamshedd jamshedd added the User Story A single user-facing feature. Can be grouped under an epic. label Oct 27, 2020
@jamshedd jamshedd added Priority:2 Work that is important, but not critical for the release Cost:M Work that requires one engineer up to 2 weeks labels Oct 27, 2020
@dagood
Copy link
Member

dagood commented Nov 2, 2020

I'm trying to understand a little better what this story tracks.

  • My initial interpretation of "on the desktop" is shaky. I believe the intent is along the lines of "on my machine".
  • "The product" from the source-build point of view is the .NET SDK, but this isn't clear IMO unless you already know what source-build is.
  • Is the focus on "easily"? Or are there more significant gaps in the experience that the story's actually about?

Here's an alternative title with my current understanding of the story, does this sound right?
As a developer, I can easily build .NET from source on my machine: either the whole .NET SDK or specific parts of it

@jamshedd jamshedd changed the title As a developer I can easily build on the desktop, either the whole product or parts of the product from source As a developer I can easily build on the machine, either the whole product or parts of the product from source Nov 5, 2020
@jamshedd
Copy link
Member Author

jamshedd commented Nov 5, 2020

@dagood, you're right I did mean on my machine when I said on my desktop :) Desktop can mean different things in different contexts so machine is less ambiguous.

@danmoseley danmoseley changed the title As a developer I can easily build on the machine, either the whole product or parts of the product from source Developers can easily build locally from source all or part or .NET 6 Nov 30, 2020
@danmoseley
Copy link
Member

@jamshedd is this Linux only? If so that should be in the title. (Obviously all OS can be built from source, but it's Linux that we're making it easiest)

@dagood dagood changed the title Developers can easily build locally from source all or part or .NET 6 Developers can easily build locally from source all or part of .NET 6 Nov 30, 2020
@jamshedd jamshedd changed the title Developers can easily build locally from source all or part of .NET 6 Developers can easily build locally from source all or part of .NET 6 on Windows, Linux, and Mac Dec 2, 2020
@jamshedd
Copy link
Member Author

jamshedd commented Dec 2, 2020

@jamshedd is this Linux only? If so that should be in the title. (Obviously all OS can be built from source, but it's Linux that we're making it easiest)

I updated the title to make it obvious this is all 3.

@danmoseley
Copy link
Member

@jamshedd could you say more here about the motivation for Windows? The motivation for Linux is clear -- so that distros can build from source.

@dagood
Copy link
Member

dagood commented Dec 10, 2020

I'd also like to hear more about this. (Note that dotnet/source-build doesn't support Windows.)

Side note: Homebrew now builds .NET Core for macOS using dotnet/source-build thanks to community effort, and historically dotnet/source-build has supported running on macOS. So there's also motivation there, like Linux.

@Fasjeit
Copy link

Fasjeit commented Jan 14, 2021

+1 for desktop builds.

We have a full fork for dotnet runtime 3.1 with custom crypto. The plans are to ship this modified runtime and SDK to customers to build apps with native GOST algorithms (Russian crypto) support in dotnet (including ASP.NET, X509, CMS, XML, etc.) both in Windows, unix, and mac. Many people already happy using it.

And even building runtime in 3.1 is real pain thanks to netstandard. It would be nice to have a fully offline build in 6.0, where we can build full dotnet runtime and SDK from modified sources without messing with CI pipelines and tons of API Compat issues.

@dleeapho
Copy link

Given the effort cost of higher pri epics and the diffuseness of the motivation for this epic we don't believe this work fits in the 6.0 timeframe.

@Fasjeit desktop and fully offline builds for Linux and macOS is supported in 5.0 and we will maintain it for 6.0. If you encounter specific issues please file them at https://github.com/dotnet/source-build/issues

@mairaw
Copy link
Contributor

mairaw commented Jan 14, 2021

Should this be moved to Cut then @dleeapho?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cost:M Work that requires one engineer up to 2 weeks Priority:2 Work that is important, but not critical for the release Team:Acquisition & Deployment User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

6 participants