forked from dotnet/msbuild
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow overriding fallback paths for MSBuildExtensionsPath via a prope…
…rty (dotnet#59) * Add support for fallback paths to be specified via property references Currently, the list of fallback paths in app.config can have a property reference, like: ``` <searchPaths os="osx"> <property name="MSBuildExtensionsPath" value="$(FallbackPath);/x/y/z" /> ``` .. but it is assumed that such a property will expand to a single path. This commit adds support for such properties to expand to multiple ';' separated list of paths. The rules for expansion do not change, they are still expanded at the time of project import. With this, given `$(FallbackPath)="/a/b/c;/q/w/e"` and the list of fallback paths would become `"/a/b/c;/q/w/e;/x/yz"`. * [osx] Add property allowing users to override fallback paths for .. .. MSBuildExtensionsPath. For OSX, this essentially sets the fallback paths to: `<property name="MSBuildExtensionsPath" value="$(MSBuildExtensionsPathFallbackPathsOverride);/Library/Frameworks/Mono.framework/External/xbuild/" />` .. whichs allows the default fallback paths to be overridden by setting a property - `$(MSBuildExtensionsPathFallbackPathsOverride)`. One of the useful use cases for this is to be able to run tests with in-tree builds of assemblies/targets meant for `$(MSBuildExtensionsPath)/`. Simply changing `$(MSBuildExtensionsPath)` would mean that the in-tree builds of the custom frameworks would work but the default ones would not be found!
- Loading branch information
Showing
8 changed files
with
150 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.