ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Priest <>
Subject RE: Exec creates a new Shell?
Date Tue, 18 Nov 2003 22:15:57 GMT
But that was just it- we were using 8.3 filenames.

My co-worker was uses a 4nt shell as his default shell. So he sets:


The exec calls a proprietary make tool:

<target name="signcab">
     <exec executable="${BMAKE}" failonerror="true" >
        <arg line="-dCAB_FILE=${cabfile} ${NATIVE_SOURCE}signPWFTcab.mke"/>


<property name="BMAKE"   value="${DMS_SOURCE}util/bin/bmake.exe"/>

that path equates to: "D:\pw\src" which as you can see, is not what the
command was complaining about. It was complaining about the "E:\Program" and
his ComSpec was specified with the 8.3 dirname\filename. So that is what led
me to think that maybe it was being "expanded" properly. In all his other
paths he uses 8.3, except for a few path includes in his "Path" dir. But I
think it has something to do with the path for 4NT.exe.

When we switched the ComSpec env var back to using cmd.exe it all worked


-----Original Message-----
From: Christopher Schultz []
Sent: Tuesday, November 18, 2003 4:36 PM
To: Ant Users List
Subject: Re: Exec creates a new Shell?

>> Okay. I can buy that. But do you have any suggestions to solve my 
>> original problem.
> Yep: modify the ant.bat bootstrap script that everyone uses to st 
> (or whatever it's supposed to be)

Wait; sorry. That wasn't the problem.

Try this: check your script to see what it's trying to call (C compiler, 
etc.). Try to express the path to this program without using spaces, 
like using the old-skool 8.3 syntax for the path names.


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message