Hi!
I found a very disturbing behavoiur of NAnt (I'm using 0.85rc3)
Let us suppose I have a following build script:
<?xml version="1.0"?>
<project name="lib1" default="all" >
<target name="all">
<csc target="library" output="lib1.dll">
<sources>
<include name="*.cs" />
</sources>
<references>
<include name="lib2.dll" />
</references>
</csc>
</target>
</project>
and now let's say I placed my lib2.dll somewhere around, but not in
the place visible to nant/csc. Now what happens is that I get errors
about unknown types and namespaces from C# compiler. But I say to
myself, "Hey, how is this possible? I just included my lib2.dll in
reference, WHY is it complaining. And after some time of debugging and
enabling -v flag of Nant I realise that Nant isn't passing the
/reference:lib2.dll to compiler at all.
Hm... not good. NAnt is trying to be smarter than me and leads me to
the place where I'm not sure what is happening. What I expected was to
get a familiar message from csc that it can't find the lib2.dll file.
I really specified that I want this reference and I know what I'm
doing.
OK, so there are two points:
- why NAnt is not passing the options I specified to the compiler?
- why NAnt is not issuing an error or warning, that the assembly I'm
referencing is not visible?
PS: my real problem is that I'm using the custom CompilerTask, which
is invoking compiler with different rules of searching assemblies than
csc and what NAnt considers as invalid reference is completely valid.
--
Kamil Skalski
http://nazgul.omega.pl
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
