I figured out my problem.
I had to set Configuration Properties > Linker >
General > Ignore Import Library > Yes
From: Rami Abughazaleh
Sent: Sat 4/29/2006 5:22 AM
To: nant-users@lists.sourceforge.net
Subject: Why would nant's <solution> task attempt to link with a non-existent lib file?
Hello.
I have a VC++ 2003
solution that has several projects that I am trying to build with the
<solution> task.
I have a project
named "Service" that generates an exe used as a windows service for the
application.
This project has an
idl file that is used by midl to generate a tlb.
The tlb file gets
generated correctly.
However, I have
another project called "SystemTray" that #includes the generated header file
that contains the interfaces from the "Service" project.
During nant's
<solution> compilation of the "SystemTray" project, I get the following
error:
[solution]
Starting solution build.
[solution] Building 'MainApplication' [Release] ...
[solution] Building 'Service' [Release] ...
[solution] Building 'SystemTray' [Release] ...
[link] Linking 114 files.
[link] LINK : fatal error LNK1181: cannot open input file 'C:\ProjectName\SRC\Service\Release\Service.lib'
[solution] Building 'MainApplication' [Release] ...
[solution] Building 'Service' [Release] ...
[solution] Building 'SystemTray' [Release] ...
[link] Linking 114 files.
[link] LINK : fatal error LNK1181: cannot open input file 'C:\ProjectName\SRC\Service\Release\Service.lib'
BUILD FAILED - 0
non-fatal error(s), 2 warning(s)
External Program
Failed: link (return code was 1181)
Total time: 11.7
seconds.
Why would nant's
<solution> task think there should be a lib file and attempt to link with
it?
Any ideas on how to
work around this issue?
(The
solution builds correctly in VS2003)
I am using NAnt 0.85 (Build
0.85.2308.0; nightly; 4/27/2006).
Thank
you.
-Rami
