Simon,

Can you submit a bug report for this issue here :
http://sourceforge.net/tracker/?atid=402868&group_id=31650&func=browse, and
attach a repro for these issues ?

Thanks,

Gert
----- Original Message ----- 
From: "Simon Steele" <[EMAIL PROTECTED]>
To: "Nantdev" <[EMAIL PROTECTED]>
Sent: Monday, March 22, 2004 7:03 PM
Subject: [nant-dev] VC++ Solution Build - bad build directory


> Hi,
>
> I've just tried the latest nightly build for building c++ projects in
> solutions - it's much better! Thanks! I'm still not quite there for my
whole
> solution though.
>
> The solution I'm building has a Managed C++ project which is then used
from
> C# projects. The mc++ project now builds correctly which is an
improvement.
> Unfortunately the solution build then can't find the build result to
> reference it later on.
>
> There are two reasons for this.
>
> The first is that I think the OutputPath property of VcConfiguration is
> wrong. It tries to combine the OutputDirectory of the project with the
> output directory of the tool. My tool output directories are relevant to
the
> project not to the output directory.
>
> This property works better:
>
> public override string OutputPath {
>     get {
>         string linkOutput = GetToolSetting("VCLinkerTool", "OutputFile");
>         if (linkOutput != null) {
>             return Path.Combine(ProjectDir.FullName, linkOutput);
>         }
>
>         return Path.Combine(ProjectDir.FullName,
> GetToolSetting("VCLibrarianTool", "OutputFile"));
>     }
> }
>
> I have checked that this holds true for two different VS.NET created
managed
> c++ projects. If there are cases where the linker output is relevant to a
> different path then maybe this needs a bit more logic.
>
> The second problem is that the reference resolver tries to load the result
> of the mc++ build to find out what it references. This can never work in
> this case because the dll is linked to another DLL which is built
elsewhere.
> The solution can't build these to the same directory because of nasty
visual
> studio lock problems caused by intellisense.
>
> I think that if the reference resolver fails to load an assembly with the
> error below and the file exists that it should still copy that assembly.
>
> "File or assembly name pdgwrapper_mcpp.dll, or one of its dependencies,
was
> not found."
>
> What do you think?
>
> Thanks,
>
> Simon.
>
> -- 
> Simon Steele
> Research Engineer - Softel Ltd.
> tel: +44 118 984 2151 / web: http://www.softel.co.uk/
> <http://www.softel.co.uk/>
>
>
> ________________________________________________________________________
> This e-mail has been scanned for viruses by MessageLabs.



-------------------------------------------------------
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_id=1470&alloc_id=3638&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to