yup thats quite possible. Though I wanted to do all from a single perl script.But, its also not so bad to create another wrapper which will be using the script.
Thanks Poonam On 12/21/05, Xavier Noria <[EMAIL PROTECTED]> wrote: > > On Dec 21, 2005, at 12:32, Poonam Pahil wrote: > > > Thanks for replying John. > > > > iam having a very limited choice in modifying the design.let me > > explain. > > I want to write a perl script to automate the build process. > > The normal manner is - > > modify a file. > > set up the build env.(use a *.cmd file) > > start the build. > > > > I don't want to perform all this manually every time i make an exe. > > so i > > wrote a perl script. > > To set up the env. I have to use the *.cmd file . doing similar > > things in > > the script will not be good. The only way i can do this is to use > > system or > > exec() > > I need control back so i use system. > > In unix u can use the dot operator to make changes to the current > > shell(env.). i have no idea in case of windows. > > can you suggest anything better. > > What about a .bat wrapper? Something like > > @echo off > set_environment.cmd > perl project_builder.pl > > There, project_builder.pl does not call to system(), it has the > environment already set. > > -- fxn > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> > > >
