Skip to content

Conversation

@asklar
Copy link
Member

@asklar asklar commented Sep 12, 2020

Fixes #741
This is hit when forcing proc count in msbuild since /MP should also imply /FS (force synchronous writes) but that enforcement is done by FixupCLCompileOptions after all other ComputeCompileInputsTargets runs. If something runs after the fix up has already happened, we break the build (Error C1041: cannot open program database)

@asklar
Copy link
Member Author

asklar commented Sep 12, 2020

CC @kennykerr. Looks like the C++ for WinRT Xlang internal Build task is stuck, mind kicking it?

@kennykerr
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@kennykerr
Copy link
Collaborator

I just need @Scottj1s or @jlaanstra to review the msbuild goo.

@asklar
Copy link
Member Author

asklar commented Sep 13, 2020

CC @yuehuang010 @olgaark to double check me

@asklar asklar marked this pull request as draft September 14, 2020 04:49
@asklar asklar marked this pull request as ready for review September 14, 2020 07:39
@kennykerr
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@kennykerr kennykerr merged commit 2a0a7fa into microsoft:master Sep 15, 2020
@jlaanstra
Copy link
Contributor

This change breaks the razzle build with error MSB8027: Two or more files with the name of XamlMetaDataProvider.cpp will produce outputs to the same location. This can lead to an incorrect build result.. Need to revert.

@jlaanstra
Copy link
Contributor

Turns out this is actually a bug in razzle. I'll send mail with details since this is a problem with an internal tool.

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.

Build breaks when adding to ComputeCompileInputsTargets because FixupCLCompileOptions doesn't run at the end

3 participants