[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-patch] Scanner config discovery, part 2
|
The path/symbol properties page seems to be able to detect when a
project is missing this new builder, why not just put a button that lets
the user fix this in this page? Or better yet, just add it when the path
discovery is enabled for the first time.
Dave.
Vladimir Hirsl wrote:
On top of below mentioned changes this patch adds:
Migration from 1.2.X and 1.0.X make projects to 2.0 project format (upon
startup, opening or import of the project and as a toolbar action).
A fix for proper handling of "." include paths.
Minor changes in the make build output parsing.
Thanks,
Vmir
The second 'Scanner config discovery' patch contains following changes:
Core
Improved translation of relative include paths to absolute. There are
still cases where the translation will fail (in case the working directory
cannot be determined) in which case problem markers are created.
The scanner config nature (and builder) are now always on. The main
checkbox now enables/disables further contribution to the discovered
scanner configuration, but the management of the discovered scanner config
is always on.
A new DiscoveredScannerInfoProvider and DiscoveredScannerInfo to persist
scanner configuration. They MakeScannerProvider and MakeScannerInfo are
reused to persist user specified part of scanner config. (Currently
discovered scanner configuration is stored in the .cdtproject file)
UI
Scanner config preference page, property page and New Standard Make C/C++
Wizard's scanner config tab are replaced with the
ScannerConfigOptionsDialog dialog accessible from Paths and Symbols tab of
the New Make Project preference page, C/C++ Make Project property page
and New Standard Make C/C++ Wizard.
Paths and Symbols tab has become a summary page; management of include
paths is delegated to the new ManageIncludePathsDialog dialog whilst
management of symbol definitions is delegated to the new
ManageDefinedSymbolsDialog dialog.
Future work items:
Store discovered scanner configuration in make.core plugin's state
location instead of in the .cdtproject file.
Replace information problem markers with tracing.
Add DiscoveredScannerInfo related JUnit tests to StandardBuildTests.
Add a build console for ExternalScannerInfoProvider.
