Re: [cdt-dev] CDT project view: How to programatically update the direct

[Martin Weber <fifteenknots505@xxxxxxxxx>]

Am Dienstag, 21. November 2017, 19:32:00 CET schrieb Doug Schaefer:
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> > Behalf Of Martin Weber
> > Sent: Tuesday, November 21, 2017 2:22 PM
> > To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
> > Subject: Re: [cdt-dev] CDT project view: How to programatically update the
> > directories shown below 'Includes'?

...
> > Will the project explorer then show an include folder? I`am not the only
> > one who finds it useful.
> 
> What do you find it useful for? Do less knowledgeable users also find it
> useful?

I find it useful to easily browse header files of third party libraries (e.g. 
/opt/example.org/ccdl/include). 
Or cross-compilers that are NOT located below well known dirs like/usr/include 
(e.g. /opt/mingw32/include).
Or take a header-only library like boost. On windows, there are no standard 
dir location where libraries are installed. A tool like cmake will can find 
the library anyway and if its headers are browsable for end-users, that will 
be benefit.

> 
> And besides, it's a lie. Each source file can have its own list of Includes

Yes, I know it's a lie.
But I see it for just browsing header files: It does not have to reflect each 
source file include path. And IMHO, a per-source-file-list of include path is 
confusing co-workers.

Martin

-- 
Cd wrttn wtht vwls s mch trsr.