On Thu, Apr 23, 2009 at 02:13:47AM +0200, Gregor Best wrote: | > Actually I cannot tell the difference between setting the env-variable | > and using VARIABLE=VALUE program, but that did it and that's something | > not being described in the wiki nor the man page. To get the app to work | > I used | > | > $ AWT_TOOLKIT=MToolkit ./application.sh | > | > That did it.
That is setting an environment variable.
| That's quite odd, because the only difference between the two is that
|
| $ AWT_TOOLKIT=MToolkit ./foo.sh
|
| only has effect on foo.sh while
|
| $ AWT_TOOLKIT=MToolkit
$ export AWT_TOOLKIT
| $ ./foo.sh
| $ ./bar.sh
|
| has effect on both foo.sh and bar.sh.
Don't forget to export the variable to the subprocesses. That is
probably the difference. (or if a non-POSIX shell is being used, that
could be different as well)
For bash/zsh type shells you can conveniently set and export the
variable in one command:
$ export AWT_TOOLKIT=MToolkit
-Derrick
--
One OS to rule them all, one OS to find them,
One OS to bring them all and in the darkness bind them,
In the Land of Redmond, where the Shadows lie.
www: http://dman13.dyndns.org/ jabber: [email protected]
signature.asc
Description: Digital signature
