#!/usr/bin/perl
use strict;
use warnings;
$|++;


my $cmd = 'hello world.bat';
my @cmd_args = qw/ testing testing 1 2 3 /;
my $exit_code = system( $cmd, @cmd_args ); 
print 'exit code from ', $cmd, ' is ', $exit_code, $/;
[download]

echo hello world!
echo %1 %2 %3 %4 %5
[download]

~Particle *accelerates*

This is it, but I don't think it will be of much help. In order to use "/USEENV", I first have to execute the batch file: 'vcvars32.bat'. If I execute it fromt he command line, things work fine, but when I call it in my script they don't

sub Build
{
    my $vcvars32 = 'VCVARS32.BAT';
    system ($vcvars32);

    $command = join("", "msdev ", "$workspace", "\\", "$projectname ",
+ "\/MAKE ", "\"$name ", "\- ", "$activeconfiguration\" ", "\/REBUILD 
+\/OUT ", "$workspace\\", "$log_name ", "\/USEENV"); 

    $start = localtime time;
    
    print "\nProcessing build...";
    system "$command";
    print "Done\n";

    $finish = localtime time;
}
[download]

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.

If this doesn't help, can you specify what you mean with When it executes in the script it acts as though it has executed but in reality it hasn't - maybe with a small code example?

-- 
Joost       downtime n. The period during which a system
            is error-free and immune from user input.
[download]

Unfortunatley, I can't provide the code, because it's dealing with the 'vcvars32.bat' file (environment for Visual Studio 6.0) I get the message: "Setting environment for using Microsoft Visual C++ tools.", but it hasn't actually changed the environment. If I execute the batch file from the command line and then run my perl script is works fine....DAMN Microsoft!

execution path:

run perl script -> start new environment space and run batch file -> return to old environment space inside perl script (no changes made to environment)

check out tye's SetEnviron.bat for more info on your real problem.

~Particle *accelerates*

Mmmm... Nice problem

Here's my guess:
It _does_ adapt your envirnoment, but the valuea are set back once the perl script ends...

er formait hyarya.
-- "Life is a house and the next tornado is never far away"
-- "lovely by nature"

unless(-e "yourscript.bat") {
print "Cannot see yourscript.bat...\n";
}
[download]

OK, I think this might have something to do with it. It can't see the .bat file, but I'm able to execute it from the command line in the same directory as my perl script.

Ah...perhaps the .bat file is in a directory in your %PATH% env variable...try hardcoding the entire paths in your script...remember to escape the \ characters for win32 paths...so "c:\mydir\myfile" would be "c:\\mydir\\myfile"
-Jason

~~rob
____________________________________________________________
eval pack "h*", "072796e647022245d445f475454494c5e622b3";