config env script help building gradle from perl script (system/open tips needed)

[gj2666]

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...

if ($pvob eq "XYZ"){...}
else {  open("..\\abc-env\\setenv.cmd");
    system(set);    
    system("gradle");
...}

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.
(Or I suppose, help with syntax on stringing together the commands in the same open()?). This script has never worked for this app. (btw first thing I did was put in use strict and warnings so if you've taught me nothing, you've taught me that.)

[Corion]

Why not simply write a batch file (using Perl) that invokes the environment setup, and afterwards invokes that gradle command?

call ..\\abc-env\\setenv.cmd
call gradle

As an alternative, you could try a technique like Get default login environment except for Windows, and then stuff these changes into %ENV.

[gj2666]

I'm not sure I see how your suggestion is different than what I'm doing? Referencing PerlDoc I only see system(), ``, open(), and exec() as ways to execute commands in the shell. What am I missing?

[Corion]

My suggestion is different because batch files executed by cmd.exe modify the environment of the cmd.exe process they are called in.

[BrowserUk]

If you set values into %ENV before calling system, then commands or programs run via system will see those changes,

C:\test>set fred
Environment variable fred not defined

C:\test>perl -E"$ENV{fred}='bill'; system q[set fred]";;
fred=bill

[gj2666]

Now at least that idea did not break my brain. Unfortunately the syntax will likely make me stabby. (been battling hashes of arrays syntax all morning. Hashes are hard like Lewisian Gneiss).