Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Build environment variable providers?

NB I'm thinking Wascana style integration...

2009/5/22 Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>:
> Ok, just realised this isn't quite what I meant - I need to specify
> the parent environment, so to speak, so that the compiler can be found
> in the first place i.e. I need to append PATH at runtime so that the
> tools can be found. I tried doing this using the
> configurationEnvironmentSupplier extension point, but realised this
> only provides the environment inside the processes which are
> spawned...
>
> 2009/5/21 Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>:
>> Got it, thanks
>>
>> 2009/5/20 Doug Schaefer <cdtdoug@xxxxxxxxx>:
>>> The MinGW toolchain uses this. It's in the gnu.ui plugin.
>>>
>>> Doug
>>>
>>> On Wed, May 20, 2009 at 11:51 AM, Mike Wrighton
>>> <mike.wrighton@xxxxxxxxxxxxxx> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Is there an extension point to specify build environment variable
>>>> providers (e.g. PATH during a build) or it is API only? All I could
>>>> find was BuildBuildData.getBuildEnvironmentContributor()
>>>>
>>>> Thanks,
>>>> Mike
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>>
>>
>


Back to the top