Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Environment variables not passed to make

> How about this idea:
> All CDT invocations of command line tools of any significance goes =
> through the ProcessFactory and Spawner classes.  One could patch the =
> ProcesFactory.addPathsToEnv() method to add paths to the PATH =
> environment variable for the exec() command invocation from a defined =
> extension point.  The extension point could be defined for the =
> configuration to apply to all CDT.  A preferences page for CDT could be =
> added to allow the user to add/remove/edit paths.  To make the path in =
> the extension point portable and not hard-coded, one could make an =
> interface for the extension point that dynamically provides the full =
> path values.

Is this the right approach ?
What about if I do not want to spawn with the default environment(the one set in the preference).
Or if I want to override one environment variable for a specific action ... say the build.

So far we can set the environment:
- when launching
- when building

What other places do you need to set environments ?

Back to the top