[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Environment Management and Run Configurations
|
Yes, the launch code checks the project associated with the launch configuration to see if modules are enabled. If so, it will obtain the command string that must be executed to configure the environment and make this available as the "ems" attribute. Configurations can then add "${ptp_rm:ems#value}" to the submission script so the commands are executed prior to running the application. The "edu.sdsc.trestles.torque.batch" configuration uses this.
Let me know if you need more details.
Greg
On Nov 12, 2012, at 2:50 PM, John Eblen <jeblen@xxxxxxx> wrote:
> Hi
>
> I am working on bug 393244 - Environment management module information stored at project level
>
> I have modified the EMS code so that environment information is stored per build configuration,
> and it all seems to work fine for building. (I can now specify a different set of modules for each
> build configuration.) Specifically, this change stores the data entered on the environment properties
> page to a different location (currently .cproject). It is no longer stored per project.
>
> However, I want to make sure this change doesn't break remote launch. I can't seem to find
> any remote launch code that accesses a project's environment information. However, I do see
> some use of environment management in the rm code. How does remote launch use the EMS?
> Does it need access to the data, such as the list of modules, which are configured on the
> environment properties page?
>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
