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

Support the nmakeobj path and the standard intermediate output path for compile_commands.json on Windows. #322

Merged
merged 2 commits into from
Mar 17, 2021

Conversation

jkoritzinsky
Copy link
Member

Required for dotnet/runtime#49715

cc: @dotnet/jit-contrib for review.

Copy link
Member

@BruceForstall BruceForstall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is nmakeObjCompileCommands still here just to support people who haven't updated to the newest (PR'ed) dotnet/runtime? Or do we check both paths for some other reason, like cmake might put things in a different place in some scenarios? it might be helpful to add the answer as comments in the code.

@jkoritzinsky
Copy link
Member Author

Yes, it's just here for backcompat. I'll add a comment in the code.

@jkoritzinsky jkoritzinsky merged commit 945715f into dotnet:main Mar 17, 2021
@jkoritzinsky jkoritzinsky deleted the fallback-path-jitformat branch March 17, 2021 16:23
jashook pushed a commit to jashook/jitutils that referenced this pull request Mar 8, 2022
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.

2 participants