Well, as I'm finding out, you can specify a target once you call the slingshot task but you have to have prior knowledge of what it generates. As stated below, it defaults to the Debug target but when you call the <nant> task, you can specify the Release target if the build is a release build. At least that is how I'm doing it.
As for C++ support, I seem to remember it only supporting C# and VB.NET. I wouldn't take my word for it though as I am a newbie (for now ;~)
Good luck
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
-----Original Message-----
From: Castro, Edwin Gabriel (Firing Systems Engr.) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 31, 2004 2:04 PM
To: [EMAIL PROTECTED]
Subject: RE: [Nant-users] Slingshot Question
Hello All,
Slingshot looks like a cool tool! Can I specify a different Target? Also, does it support VC++ projects?
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
________________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bonnett, Evan A
Sent: Wednesday, March 31, 2004 9:28 AM
To: [EMAIL PROTECTED]
Subject: [Nant-users] Slingshot Question
All,
When slingshot generates the build file, its default target is debug.
<project name="ApplicationLauncher" default="Debug">
But when my debug property in the the calling build file (the file that calls slingshot) is false, it still calls the debug target. Any idea on why? Here is the target that calls slingshot:
<target name="build" depends="getsource">
<mkdir dir="${build.basedir}\${basename}" />
<slingshot solution="ApplicationLauncher.sln" format="nant" output="${source.basedir}\ApplicationLauncher.build">
<parameters>
<option name="build.basedir" value="${build.basedir}\${basename}" />
</parameters>
</slingshot>
<nant buildfile="${source.basedir}\ApplicationLauncher.build">
<properties>
<property name="build.dir" value="${build.basedir}\${basename}\bin" />
</properties>
</nant>
</target>
Now, the csc call in the generated build file looks like this...
<csc target="winexe" output="${output}" debug="${debug}" define="${define}" doc="${doc}" warninglevel="${warninglevel}"> The ${debug} property is not defined in the file so I assumed that it was the property that I am setting in the calling file. But, if that's the case, it should be false. Help?
Evan A. Bonnett
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
