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

Mop up sharedfx tool package migration; GeneratePackageOnBuild feedback fix #4073

Merged
merged 3 commits into from
Oct 7, 2019

Conversation

dagood
Copy link
Member

@dagood dagood commented Oct 7, 2019

Ports a couple of changes that were made to framework.dependency.targets in Core-Setup before its copy of these targets were deleted. (I linked origin commits in the commit descriptions.)

One is still in progress (dotnet/core-setup#8468, Enable building for arm64 on arm64) but I anticipate it going in soon.

Also fixes #4035. Removing GeneratePackageOnBuild saves devs some time by avoiding building the sharedfx SDK nupkg unnecessarily. (FYI @alexperovich)

Ports fix made to sharedfx targets before Core-Setup migrated to the shared tooling SDK.

dotnet/core-setup@b903a6e
Ports fix made to sharedfx targets before Core-Setup migrated to the shared tooling SDK.

dotnet/core-setup@558f70f
Describe why GeneratePackageOnBuild is necessary for the Arcade SDK project and removes it from the sharedfx tooling project, where it isn't needed.
@dagood dagood self-assigned this Oct 7, 2019
@dagood dagood merged commit b141558 into dotnet:master Oct 7, 2019
@dagood dagood deleted the shared-sfx-tools branch October 7, 2019 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why does the Arcade SDK project enable GeneratePackageOnBuild?
2 participants