|Do you know where your variables are?|
config env script help building gradle from perl script (system/open tips needed)by gj2666 (Beadle)
|on Jun 11, 2013 at 15:53 UTC||Need Help??|
gj2666 has asked for the
wisdom of the Perl Monks concerning the following question:
I inherited a win (2003) perl (5.16.2) build script combining steps in a build process for multiple apps. For one of the apps we build with Gradle.
I'm having a difficult time with the environment setup. Here's a snip...
I know that the open is in one (session/stream/fork/process?) and that as soon as it returns, all the environment it has just set is lost. I did the "system(set)" to confirm that point.
So when I execute the "gradle" it fails because there isn't anything in the env session where the system("gradle") is executed.
I read the "open()" perl doc and it looked like maybe you could create a pseudo filehandle that could be reused later in the calling script. But that sounded too good to be true. if so, syntax? Redirect or pipe new command into the filehandle?
I understand what open() or system() etc. is doing, but I've never really understood how to work with the configuration of such a temporary environment. The env is set for each build target so setting it at the os level doesn't really work for me in this case.
Any suggestions for getting the env variables to be persistent from within the build script would be appreciated.