Hello!
I have now tried to implement an External Settings Provider, but
some things are a bit unclear to me.
1) How External Settings Provider adjusts to different locations in
different machines? Does this happen automatically or if not then
what checks or tricks should one implement?
2) Pkg-config outputs OS-specific paths so does External Settings
Provider work cross-platform as well?
3) How to add a value to "Other flags" field in Compiler's
Miscellaneous group? ICSettingEntry doesn't exist for that.
4) For some reason
ICConfigurationDescription#setExternalSettingsProviderIds doesn't
have effect on AbstractCPropertyTab#updateData but works via
preference page or pop-up menuitem etc. Any ideas what's wrong?
As a side note this approach seem to take more time.
Cheers,
Petri
On 06/14/2011 12:34 AM, James Blackburn wrote:
On 13 June 2011 15:26, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx>
wrote:
Hmm, the idea behind pkg-config is that I can take the same
project to a different machine where the packages are
installed in a different location and have the build
automatically adjust to the new location. I've been using that
capability planning with Wayland. The paths are dynamic and
shouldn't be hardcoded in the build settings. Mind you, that
makes things a lot more difficult.
We support this already using the ExternalSettingsProvider
extension point. (We use this hook successfully here to
plumb in our SDK paths which change frequently.)
At any rate, what I've done in the past is implement a
pagesAfterTemplateSelectionProvider. When the wizard is
finished it asks the pages for a dictionary of string/value
pairs that are passed down to the template processes.
Yep, that's what I'd do.
Cheers,
James
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
