Skip to content
This repository was archived by the owner on Jul 14, 2020. It is now read-only.

autoimport build packages if also modules#119

Merged
kingerja merged 7 commits intoCommonBuildToolset:masterfrom
kingerja:iss44
Jun 2, 2017
Merged

autoimport build packages if also modules#119
kingerja merged 7 commits intoCommonBuildToolset:masterfrom
kingerja:iss44

Conversation

@kingerja
Copy link
Copy Markdown
Contributor

Automatically enable import of any build imports if it is also a cbt module package.

@kingerja kingerja requested a review from jeffkl May 31, 2017 22:45
foreach (BuildPackageInfo buildPackageInfo in ModulePaths.Select(BuildPackageInfo.FromModulePath).Where(i => i != null))
{
ProjectPropertyElement enableProperty = propertyGroup.AddProperty(buildPackageInfo.EnablePropertyName, "false");
bool defaultEnableValue = false;
Copy link
Copy Markdown
Contributor

@jeffkl jeffkl Jun 1, 2017

Choose a reason for hiding this comment

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

Okay I finally understand what you're trying to do. If its a module because it has a module.config, its imported by default. However, there's no guarantee that people will be using the CBT.NuGet module in their code bases. So if all modules have a layout like:

CBT.Traversal
  └─build
      CBT.Traversal.props
      module.config
      Traversal.targets

And we eliminate the proprietary build.props, then we want them to work with or without the CBT.NuGet module. So CBT.Core should import CBT.Traversal.props like it does build.props and CBT.NuGet should only generate imports for build packages that are not modules.

@kingerja kingerja merged commit aec1b83 into CommonBuildToolset:master Jun 2, 2017
@kingerja kingerja deleted the iss44 branch June 2, 2017 23:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants