Re: Setting environment-variables in Eclipse (EPIC)?

If the variable in question is PERL5LIB, you can also add paths by right-clicking the project, choosing Perl Include Path, and adding ${project_loc}/lib or whatever.

I have already put the appropriate export statements in the .profile shell-script...

Then one would conclude that .profile isn't getting executed. Perhaps you are using a GUI? For KDE, I created the following shortcut:

$ dir .kde/env/
total 0
lrwxrwxrwx 1 eric users 24 Jan 20  2009 profile.sh -> /home/eric/.bash
+_profile

$ cat .bash_profile
...
export PATH=~/usr/perlbrew/bin:~/usr/perlbrew/perls/current/bin:$PATH
export PERLBREW_ROOT=~/usr/perlbrew
...
[download]

Surely there's something similar for OS/X.

This way, you can solve the problem for all applications, not just Eclipse.

Comment on Re: Setting environment-variables in Eclipse (EPIC)? Select or Download Code

Replies are listed 'Best First'.
Re^2: Setting environment-variables in Eclipse (EPIC)? by locked_user sundialsvc4 (Abbot) on Mar 16, 2011 at 15:26 UTC
Thank you for your suggestions, but let me clarify a couple of points: The problem isn’t `PERL5LIB`, but environment variables. (EPIC does have a well-defined and workable way to specify the Perl include-path .. `@INC` ... to use for a particular project.) The behavior that is adversely affected by the lack of environment variables is simply the built-in syntax checking (red “X” in the margin to the left of a line, indicating an error was found there). You can set the environment-variables that are associated with a GUI icon in OS/X, as detailed in the Apple technical article (third bullet point in the OP). What I would “like to have” is the ability to specify environment variable settings, as well as the `@INC` path, on a per-project basis. However, in any case, the impact to me is negligible, and the code in question is definitely “the odd man out.”

Replies are listed 'Best First'.

Re^2: Setting environment-variables in Eclipse (EPIC)?
by locked_user sundialsvc4 (Abbot) on Mar 16, 2011 at 15:26 UTC

Thank you for your suggestions, but let me clarify a couple of points:

The problem isn’t PERL5LIB, but environment variables. (EPIC does have a well-defined and workable way to specify the Perl include-path .. @INC ... to use for a particular project.)
The behavior that is adversely affected by the lack of environment variables is simply the built-in syntax checking (red “X” in the margin to the left of a line, indicating an error was found there).
You can set the environment-variables that are associated with a GUI icon in OS/X, as detailed in the Apple technical article (third bullet point in the OP).

What I would “like to have” is the ability to specify environment variable settings, as well as the @INC path, on a per-project basis. However, in any case, the impact to me is negligible, and the code in question is definitely “the odd man out.”