Okay I have an issue that needs solving ASAP. I am using the solution task to build the entire project solution and I use the setenv task to set the include and lib folders. This seemed to work as the projects would all build without any errors about not finding the include or lib paths. But since these builds were only used for testing the build scripts and not actually used in install and product testing I did not notice the problem with the built files.
We are now going full production on the Nant builds and therefore when the product output of the build was placed into an Install and tested we found out that it would not work on 98 machines. It took us a bit, but we have tracked down the issue to be that the Nant build, by solution task, does not discard specific libraries that are to be discarded at the end of the project build. Here are the libraries that are discarded normally from the build of a project when built by Studio .NET 2003: LINK : warning LNK4089: all references to 'OLEAUT32.dll' discarded by /OPT:REF LINK : warning LNK4089: all references to 'SHELL32.dll' discarded by /OPT:REF LINK : warning LNK4089: all references to 'imagehlp.dll' discarded by /OPT:REF LINK : warning LNK4089: all references to 'ole32.dll' discarded by /OPT:REF But when built by Nant the only library that is discarded is: LINK : warning LNK4089: all references to 'OLEAUT32.dll' discarded by /OPT:REF So we looked into this a little more and noticed that if we place the Microsoft Platform SDK include and lib paths further down in the list of paths to set then even Studio would also only discard that first library one. So as long as the Platform SDK was declared at the beginning of the LIB and INCLUDE paths the Studio would build the app properly and discard the correct libraries. So I made sure using the setenv task, in NAnt, that I declared the Platform SDK paths to be first in the list. After setting this I rebuilt and notice that this did not affect the build at all. It still only discarded the one dll library. I still do not know if the solution task uses the environment variables correctly or is it still not using the solution/project configurations correctly. Has anyone had issues with the solution task not building the same as if you build through the Studio IDE? Now I did not want to complicate my build by having to run cl, link, ... Etc tasks separately as we should not have to if the solution task worked properly. Anyhow is there anything that I could do to fix this issue? Is there maybe a newer build of Nant that may handle solution tasks/environment variables better? We are currently using the nightly build from: nant-0.85-nightly-2005-11-13 Any help would be appreciated..... Thanks, Tim Mayert. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
