and 85229: Problem with scannerInfoCollector attribute in the toolChain schema of MBS.
Replaced ToolChain's attribute scannerInfoCollector with ScannerConfigDiscoveredProfileId in managed builder extension point definition schema. Discovery of compiler's internal scanner info for a manged project now uses specified SCD profile.
On Windows, specified profile calls cygpath to translate discovered paths.
44568 - [Managed Build] -Xlinker option requires space separator
80119 - [Managed Build] Error in the Xlinker option's generated output
The code and the manifest file have been changed to correctly deal with
the -Xlinker option. Multiple entries have separate -Xlinker options,
and there is a space between -Xlinker and the value. The space is
handled by the new option.command functionality - "${VALUE}".
77399 - Managed Make Builder mangles subdir.mk if configuration of
linked resource was changed
This was partially fixed before and was partially a user error.
Code has been added to output an error message to the console when
MBS sees a duplicate identifier in the loaded manifest files.
Partial fix:
80067 - [Managed Build] Wrong command for building in MMS
A fix has been added so that a command is not stored with a Tool
unless the user changes the value - i.e the Tool will inherit the
value from its suoer-class. There is still an error with the Gnu
makefile generator when a configuration tool and a resource
configuration tool have different commands specified by the user.
This will be fixed later.
Code to handle the case where a manifest file or project file contains a higher version number than the Managed Build System.
New JUnit tests for the new model.
Updates to some external strings.
The majority of the code changes were for dealing with the Java class attributes (buildfileGenerator, etc ).
The other bug fixes were:
When the user displays the properties of a file in a standard make file, the C/C++ category is displayed in the left pane I couldnt figure out a way to filter it out. Before the fix, the Managed Make property page was displayed and would then crash when the user selected OK. Now, it displays a label saying that this page only applies to Managed Make projects.
When the user has automatic build set, edits the properties of a configuration, selects a different configuration, selects OK when asked to save the changes, a build for the proper configuration would start but it would pick up the tool settings from the wrong configuration (the newly selected one).
There was a bug in the Option.onlyOverridesValue method where it wasnt checking for a zero-length built-ins list, and therefore returning the wrong answer.
There was a bug in adding a Tool to a ToolChain where the new Tool was added to the toolList but not the toolMap.
