|
Hi Mikhail!
Great to hear that.
FYI, I just realized that it is now necessary to create a
ManagedProject instance together with a configuration in order to be able to run
scanner discovery. I generally cannot use make or managed make natures, and no
managed project, otherwise our build system is messed up (e.g. too many
builders). It would be great if they are not required anymore,
then.
Thanks.
Best regards,
Gerhard
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Sennikovsky, Mikhail
Sent: Freitag, 23. Februar 2007
20:40
To: CDT General developers list.
Subject: RE:
[cdt-dev] Scanner discovery without build configuration?
Hi
Gerhard,
I’m going to work on
the Build system API backward compatibility next week and I’ll make sure the
Scanner discovery supports using the IProject as
before.
Thanks,
Mikhail
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Schaber, Gerhard
Sent: Friday, February 23, 2007 7:21
PM
To:
cdt-dev@xxxxxxxxxxx
Subject:
[cdt-dev] Scanner discovery without build configuration?
With the new project model, the
scanner discovery needs a build configuration. Is there any chance to use the
scanner discovery without build configuration, only with the IProject handle
as before? I want to select the discovery profile and its options only once
per project.
The most relevant methods
are
ScannerConfigProfileManager.createScannerConfigBuildInfo2(InfoContext)
ScannerConfigProfileManager.getInstance().getSCProfileInstance(IProject,
InfoContext, String);
I should mention that we have our
own build system, but want to use the scanner discovery, indexer, and views of
CDT.
|
