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.
on feature C14 lead to the discoveryof a cut-&-paste error in the plugin
manifest. The miscellaneous category in the cygwin C++ compiler spec
referred to the C++ compiler in Linux as the parent. Fixed this.
- upgrade plugin.xml files
- use PDE containers
- apply Eclipse 3.0 porting items, in particular openEditor and gotoMarker
- remove TestWorkbenches from test plugins
- globalizes the Managed Build properties pages by
externalizing strings in plugin.xml.
- also fixed an option reference to set a linux project's
c compiler debug level.
the logic for managing the makefiles in the face of a header file
modification. There seems to be a problem (maybe with the dependency
calculation) for dependants in other projects when a header file is moved,
but other than that the builder seems to respond properly.
Two of the fixes, 43614 and 43756, involved changing property files only,
which validates the extra work of externalizing strings from the start!
For 43616, I simply took the advice of the bug reporter and added the '-'
in front of the RM macro in the clean target and the include directives in
the makefile.
The largest part of the fix involves 43220. Until just now, this was a
critical bug in bugzilla, so I addressed it. It has just been downgraded
to an enhancement request. There is now a new entry widget in the linker
options for user objects. The makefile will simply add these to the final
build target's command. Most of the work was done in the plugin file and
the build model to handle the new "type" of option.
the new project wizard now filters out targets that should
not be selected by the user, and that the build model
handles inherited option references properly now.
This patch adds a "hook" for F1 help on the new managed project wizard
configuration selection page. It also adds functionality to the managed
build project property page to allow the user to edit the make command and
build artifact name. They can also add and delete configurations from a
target. There is no support for adding another target to a project in this
release.
- I have removed the binary parser selection from the
new managed project wizard and hard-coded the proper
parser ID in the plugin spec for the build model. There is
an updated JUnit test that verifies this change to the
build model.
- There is also a fix for the library problem on *nix. The
makefile pattern was also changed slightly to better
capture the dependencies between the build target and
the outputs of other managed projects.
