Re: [cdt-dev] Influencing where CDT is looking for include paths

[Andrew.Ferguson@xxxxxxxxxxx]

hi Florian,

This scenario works for me with CDT 5.0:
  (1) build pre-built content for an SDK
  (2) create a plug-in to make the pre-built index available to all 
projects
  (3) create a project lacking the appropriate include path settings
  (4) create a source file using types from the pre-built index, with no 
#include statements
  (5) use F3 on those types to navigate to the headers

Its still a good idea to set up the include paths, as some features (F3 on 
#include) seem to
need it. I can't see a reason not to set them up, even if the source tree 
is only partially
present.

If this doesn't help, please could you file a bug report* with the steps 
you've followed and
the symptoms you're seeing?

thanks,
Andrew
*https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CDT

 
> So the idea was to use the prebuilt index to get code-assist 
> features while not having the entire source stored locally. This 
> works quite well so far.
> The problem now is just that you don't want to navigate to every 
> include file in order to open and view it manually.
> (Since the files should be in the index and so it should be possible
> to get the path to them)
> It would be nicer hitting F3 popping up a new editor window showing 
> its content.
> 
> Is setting an include path the only way to do that?
> Or can i influence the action triggered by hitting F3 somehow?
> 
> Thanks,
> Florian

**********************************************************************
 Symbian Software Ltd is a company registered in England and Wales
with registered number 4190020 and registered office at 2-6
Boundary Row, Southwark, London,  SE1 8HP, UK. This message is
intended only for use by the named addressee and may contain
privileged and/or confidential information. If you are not the
named addressee you should not disseminate, copy or take any action
in reliance on it. If you have received this message in error
please notify postmaster@xxxxxxxxxxx and delete the message and any
attachments accompanying it immediately. Neither Symbian nor any of
its Affiliates accepts liability for any corruption, interception,
amendment, tampering or viruses occurring to this message in
transit or for any message sent by its employees which is not in
compliance with Symbian corporate policy.
**********************************************************************