Skip to content

Conversation

@MichalStrehovsky
Copy link
Member

This will allow specifying disjoint paths for the various inputs to ILC. Right now we require an IlcPath that has a tools subdirectory with the compiler, a framework subdirectory with the framework, and an sdk subdirectory with CoreLib and friends.

We need a way to bypass this if we want to run ILC as part of the build to either build crossgen2 with ILC or selfhost ILC. Separate properties avoid having to lay out things on the file system the way IlcPath expects.

This will allow specifying disjoint paths for the various inputs to ILC. We'll need this if we want to run ILC as part of the build to either build crossgen2 with ILC or selfhost ILC. Separate properties avoid having to lay out things on the file system the way IlcPath expects.
@ghost
Copy link

ghost commented Dec 30, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@jkotas jkotas merged commit 4b6c7ed into dotnet:main Dec 30, 2021
@MichalStrehovsky MichalStrehovsky deleted the splitPaths branch December 30, 2021 21:09
@ghost ghost locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants