[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Eclipse-wide environment variable recognition by sh ell
|
Could u provide more pointers in thie regard?
Roopa
To: cdt-dev@xxxxxxxxxxx
cc: (bcc: Roopa Mahishi/BTC/SC/PHILIPS)
Subject: Re: [cdt-dev] Eclipse-wide environment variable recognition by sh
ell
Alex Chapiro
<achapiro@xxxxxxx> Classification:
Sent by:
cdt-dev-admin@xxxxxxxxxx
g
10/20/2004 04:14 PM
Please respond to
cdt-dev
Launching any process from Eclipse using ProcessFactory class exec
methods, you can completely control environment of the new process.
roopa.mahishi@xxxxxxxxxxx wrote:
>
>
>
>We too have a list of environment variables that need to be set for
>different toolchains and correspondingly,
>makefile takes in the values of these environment variables.
>
>Presently, I'm running my (batch) file containing the environment
>variables
>on a shell and then calling "eclipse.exe".
>As eclipse is being called in the same shell as the environment
>variables,
>this arrangement is working fairly well..However, I cannot change the
>environment variables on the fly once eclipse is launched.Also,I am not
>supposed to change/modify the existing makefiles.
>
>Alex, You mention making new environment variables accessible to
>external
>tools
>would be easy. Kindly let us know how ?
>
>
>-Roopa
>
>
>
>
>
>
>
>
>
> To:
>cdt-dev@xxxxxxxxxxx
> cc: (bcc: Roopa
>Mahishi/BTC/SC/PHILIPS)
> Subject: Re:
>[cdt-dev] Eclipse-wide environment variable recognition by sh
> ell
>
> <cebarne2@rockwellcollins.
>
> com> Classification:
>
>
>
> Sent by:
>
> cdt-dev-admin@xxxxxxxxxxx
>
>
>
> 10/18/2004 09:29 PM
>
> Please respond to cdt-dev
>
>
>
>
>
>
>
>We have the need for a very flexible environment variable interface.
>Our
>plug-ins support multiple toolchains, each using/requiring different
>environment variables. So, we must allow the user to switch the
>target/toolchain on the fly, which will then use a different set of ENV
>variables. Because we couldn't manage the environment on the fly, we
>decided to place the environment creation in the makefile. Each
>target/toolchain configuration will have its own generated makefile, so
>this has worked fairly well.
>
>The downside is that we do have processes that need environment
>variables
>but are not best suited for running in makefiles or other batch scripts.
>But, because the variables must still remain dynamic, we cannot use the
>environment support with the Eclipse launcher.
>
>You mention making new environment variables accessible to external
>tools
>would be easy. How so?
>
>Chad Barnes
>Rockwell Collins Inc.
>
>
>|---------+---------------------------->
>| | Alex Chapiro |
>| | <achapiro@xxxxxxx|
>| | > |
>| | Sent by: |
>| | cdt-dev-admin@ecl|
>| | ipse.org |
>| | |
>| | |
>| | 10/18/2004 08:38 |
>| | AM |
>| | Please respond to|
>| | cdt-dev |
>| | |
>|---------+---------------------------->
>
>
>
>>-----------------------------------------------------------------------
>>
>>
>-------------------------------------------------------|
>
> |
>|
> | To: cdt-dev@xxxxxxxxxxx
>|
> | cc:
>|
> | Subject: Re: [cdt-dev] Eclipse-wide environment variable
>recognition by sh ell |
>
>
>
>>-----------------------------------------------------------------------
>>
>>
>-------------------------------------------------------|
>
>
>
>
>
>Maybe I don't understand your problem well, but I guess there is almost
>all now to set appropriate environment. If your Eclipse launch script
>(or Windows batch file) sets environment variables, javaw inherits them.
>They become available through EnvironmentReader. All processes we launch
>from Eclipse also inherit this environment. The two major things we lack
>are UI for setting additional environment variables and method of
>storing these extra settings in environment to make them available to
>external tools. Both things are easy to implement. Both of them seems to
>be not critical, just an convenience issue.
>
>cebarne2@xxxxxxxxxxxxxxxxxxx wrote:
>
>
>
>>We had the need for ENV variables as well. However, our need was
>>
>>
>during
>
>
>>the build to help locate compilers, license servers, standard
>>directories,
>>etc. We decided to define our variables in our makefile with the
>>"export"
>>command. Our UI offers an interface for defining these build-time
>>variables and then our makefile generator places the appropriate
>>"export"
>>commands in the makefile.
>>
>>The only other way we found to do environment variables was some method
>>on
>>the Eclipse command-line (a Java argument).
>>
>>Chad Barnes
>>Rockwell Collins
>>
>>
>>|---------+---------------------------->
>>| | roopa.mahishi@phi|
>>| | lips.com |
>>| | Sent by: |
>>| | cdt-dev-admin@ecl|
>>| | ipse.org |
>>| | |
>>| | |
>>| | 10/18/2004 07:46 |
>>| | AM |
>>| | Please respond to|
>>| | cdt-dev |
>>| | |
>>|---------+---------------------------->
>>
>>
>>
>>
>>
>>>----------------------------------------------------------------------
>>>
>>>
>-
>
>
>>>
>>>
>>---------------------------------------------------------|
>> |
>>|
>> | To: cdt-dev@xxxxxxxxxxx
>>|
>> | cc:
>>|
>> | Subject: [cdt-dev] Eclipse-wide environment variable
>>recognition by shell |
>>
>>
>>
>>
>>
>>>----------------------------------------------------------------------
>>>
>>>
>-
>
>
>>>
>>>
>>---------------------------------------------------------|
>>
>>
>>
>>
>>
>>
>>
>>
>>Hi,
>>Is there any way of setting an environment variable in Eclipse, which
>>gets
>>retained thoroughout the current active workspace?
>>
>>Kindly let me know if there is any way of setting the same
>>
>>Rgds,
>>Roopa
>>
>>
>>
>>
>>
>>_______________________________________________
>>cdt-dev mailing list
>>cdt-dev@xxxxxxxxxxx
>>http://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>>
>>
>>_______________________________________________
>>cdt-dev mailing list
>>cdt-dev@xxxxxxxxxxx
>>http://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>>
>>
>>
>>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
