Re: Re: Re: .bat and perl mystery

[jsprat]

As you've found out, you can't set environment variables in the parent process. When you try, you spawn a new command process, set the environment variable and exit that process, losing whatever changes you made (see perldoc -q environment or here).

What you can do is use the %ENV hash to set the environment before using VS to build your project.

I can't remember what vcvars32.bat sets, but something like this:

$ENV{LIB}='D:\VCDIR\LIB;' . $ENV{LIB}

should work, as long as it is set before you begin the build.

[Anonymous Monk]

Sorry, I'm not sure I quit understand. Should I create a child process solely for the execution of the .bat file and the use the parent process to continue running the main script?

[jsprat]

Make the changes in the script, before you start the build. These changes will be visible in any child process.

sub Build
{
  # my $vcvars32 = 'VCVARS32.BAT';  << comment out these 
  # system ($vcvars32);             << two lines

  # set your environment variables (the same ones 
  # vcvars32.bat sets) like so:
  
  $ENV{LIB}  = 'D:\MSVCDIR\LIB;'.$ENV{LIB};
  $ENV{PATH} = 'D:\MSVCDIR\BIN;'.$ENV{PATH];
  
  system $command;  # this now sees the variables set above

check perlvar for a little more info on %ENV