ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Brown" <mbr...@insightful.com>
Subject problems setting environment vars with exec on windows
Date Tue, 30 Oct 2001 02:29:43 GMT
> I have been having considerable difficulty setting INCLUDE 
> and LIB paths
> when trying to compile c code using exec with msdev on 
> windows. I have tried
> several things in the doc and mailing list archives like:
> 
> <exec dir="${myDir}" executable="msdev.exe">
> 	      <env key="INCLUDE"
> path="${shome}/sconnect;${shome}/spl;${shome}/include"/>
> 	      <env key="LIB" path="${shome}/lib"/>
> 	      <arg line="myproject.dsp /make ALL "/>
> 	</exec>
> 
> which doesn't work. Also I've tried using
> <property environment="env"/>
>     <env key="INCLUDE" path="${env.INCLUDE}"/>
> within the exec, that doesn't work either although if I do
> <echo message="Include: ${env.INCLUDE}"/>
> I can see that the var gets set appropriately.
> 
> If I try to do anything using
> <exec dir="${myDir}" executable="cmd.exe"> (or "cmd")
> the build just hangs or writes all output to the new invisible cmd
> window, which is no help.
> 
> Seems like this shouldn't be so complicated. Can anybody help?
> thanks in advance,
> Matt

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message