Maybe you could just try

in your script

1 members found this post helpful.

Example...

function foo()
{
export VARIABLE="Something"
}

Functions are executing in current environment so creating and exporting VARIABLE is the same as if you had typed it in the shell directly, or in the script and run it with source or . (dot) built-in. You can make function by writing it in the shell directly or write it in the script and run script with 'source ./script... =)

It's not a solution, but at least this is an workaround:

In your script do something like:

echo MY_VAR >/tmp/my_var.value

In the script in which you want to use the variable value, do something like this, for example:

gcc my_script.cpp -I`cat /tmp/my_var.value`

Cosmin.

This highlander thread was usefull to me as well. Cheers!

1 members found this post helpful.

I don't understand what the moderators have against people bringing up old threads. If Google returns this forum thread for a query for a common problem, it shouldn't matter how old the last post was, as long as it is still relevant.

On topic: I was having the same problem using source and export in a bash file, and the leading dot makes it so I the environmental variables appear in the command line after the script finishes. I would like to see someone demonstrate the use of functions though, so I have a second way of fixing the problem should it arise again. If anyone is inclined to include such a demo, I (and all the others who come upon this thread after me) would be very grateful.

1 members found this post helpful.

@domino1241: What do you mean by a demonstration with the use of functions.. What problem needs to be fixed?