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.
Just tweaked the logic to check for a previously selected tool or option (which the tab was storing anyway). If one was selected, that selection is made in tree viewer.
The original fix had two problems. When a source folder had only one file deleted, a complete rebuild was required because the output folder was removed. Now the generator checks.
The parent folder could be deleted accidentally, so that has also been resolved.
Finally, the dependency generator pattern ahs been simplified and now uses a Gnu make-supplied macro for calculating the directory component of a file.
The MBS now validates the configuration names more carefully. It checks for duplicates in a case-insenstive way. It also looks for invalid whitespaces at the start of a config name. It also disallows names containing \/:*?"<>
Also corrected a file that had a local variable called "enum" which is now a "sort-of" reserved keyword in Java 1.5
In ScannerInfoConsoleParserUtility
- Absolute include paths are correctly handled in translateRelativePaths(..).
- Corrected normalization of paths ending with single dot in normalizePath(..)
If there is no match for an option in the project being converted, ignore the option and continue converting the configuration
Patch tool lookup in converters to handle the case where the location of the definition fools the manifest reader and effectively hides the tool
The fix involves changing the way the updater converts model element IDs. It now tests as best it can whether the element is built-in or not before looking it up and adding it to the new, 2.1 buld model for the project
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.
1. [Bug 79451] NPEs on project import
2. [Bug 77399] Managed Make Builder mangles subdir.mk if configuration of linked resource was changed fix for initial problem additional problems to be investigated
3. Force rebuild when file build option changes
4. Ensure that converted projects get saved.
The 1.2 project stored the default project in the cdtbuild file so it was a matter of reading that it an cacheing a map of old config IDs to new, then setting the default using the appropriate new config
Fix for bugzilla 79572 -- Importing 1.2 projects with libraries/library search paths fails
The IDs for libraries and library search paths had an extra element that converter was not dealing with and the conversion was failing
