I have a number of separate "netmodules" that I would like to link
together into an assembly via the <al> task. The "netmodule" tasks
work fine and they update as expected.
My problem, is that the <al> task within my target does not always
execute. I added <echo> lines above and below the <al> task and they
are being called... but the <al> task does not execute if the output
file already exists. I was hoping that it would execute if any of the
netmodules were newer, so that I can generate a new assembly manifest.
I am specifying my netmodules in <arg> tags as follows
---------
<al verbose="true" delaysign="true" keyfile="${delaysignkey}"
win32res="${project.win32VersionResouce}" target="lib"
output="${project.assemblyName}" >
<!-- list of modules to include -->
<arg line="${build.dir}\${moduleName.a}" />
<arg line="${build.dir}\${moduleName.b}" />
<arg line="${build.dir}\${moduleName.c}" />
<sources>
<include
<include name="resource1.xml" />
<include name="resource2.xml" />
<include name="resource3.xml" />
</sources>
</al>
---------
However, when the .netmodules are rebuilt and more recent, the <al>
task does not execute. I have worked around the problem by writing
<uptodate /> and <if test=""/> code to manually delete the <al
output="${project.assemblyName}"> file if it's out of date. This
forces the <al> task to relink the netmodules and life is good.
Is this how it is supposed to work? Do need to track the <al>
dependencies myself?
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
