Re: [cdt-dev] project configurations (includes paths etc)

[James Blackburn <jamesblackburn@xxxxxxxxx>]

Hi Marc

This is the sort of thing the external setting provider extension  
point is good for. You can use it to provide additional paths to the  
build system dynamically; implementing this should be straightforward.

Cheers,
James

On 22 May 2009, at 01:44, Marc Weber <marco-oweber@xxxxxx> wrote:

> Hi,
>
> Is there an easy way to add include paths automatically?
> I'm talking about pkg-config tool or such. The easiest thing I can
> imageine is letting the user specify some project specific shell  
> scripts
> echoing a list of include paths or asking cdt to parse a bunch of  
> common
> gcc optiosn such as -Ifoo -Ibar to add those parameters itself.
> The same could be done for libraries/ lib dirs.
>
> Another option would be letting the use add a very simple addtional
> configuratio nfile such as .cproject.properites looking like this:
>
>  additional-includes: foo bar # explicitely add a list of dirs
>  parse-options: -Ifoo -IBar -Ldir -llibfoo -llibbar # make cdt  
> figure out itself what to use (ignoring unkown options)
>
> I've read about adding `pkg-config ...` to the Misc* options. However
> does cdt recognize those include paths then?
>
> I've also found a small python script (pkgconfig2cdt) which adds some
> lines to the .cproject file after you've shutdown Eclipse. I don't  
> want
> to shutdown Eclipse when trying out another set of includes/ library
> versions to compile my projects with.
>
> If there is no easy way to do this yet I'd like to spend time on
> implementing it. Maybe you can even assist me?
>
> Sincerly
> Marc Weber
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev