Bugs item #1599921, was opened at 2006-11-20 13:32
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1599921&group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adam Gritt (anxan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Build Order Error

Initial Comment:
I found that if you have a Managed C++ project in a collection of projects to 
be built, NAnt doesn't properly determine the build order or that the assembly 
was built.  NAnt works fine with VB and CS but not the CPP.  Attached is a zip 
file with a sample set of projects and a NAnt build script to demonstrate it.  
There are 2 build scripts one that builds the Cpp project first and one that 
builds it last.  Both fail because NAnt doesn't recognize that it was build in 
either case and it doesn't determine the proper build order.  If you build it 
manually (such that it copies files in the post build event) everything builds 
fine.  This includes the VB project that is listed before the CS project that 
it depends on.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=1599921&group_id=31650

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to