RE: [nant-dev] Bud Attempting a build
This release solved my problem. Thanks John Cornell Kofax Image Products Software Development Manager (949) 727-1733 Ext.336 http://www.kofax.com/ Gert Driesen [EMAIL PROTECTED] 04/04/2005 11:09 PM To [EMAIL PROTECTED], nant-developers@lists.sourceforge.net cc Subject RE: [nant-dev] Bud Attempting a build Hi John, Please upgrade to NAnt 0.85 RC2 (or a recent nightly build, http://nant.sourceforge.net/nightly/latest), as lots of fixes went into the solution task after the 0.84 release. Gert PS. Nice to know that Kofax is using NAnt ;-) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: dinsdag 5 april 2005 1:29 To: nant-developers@lists.sourceforge.net Subject: [nant-dev] Bud Attempting a build I received the following message when trying to build using NAnt. I have included the contents from my build file as well. I tried to build using both the version of NAnt that ships in the bin folder and by rebuilding NAnt on my machine. I have successfully used NAnt in the past. Machine Specs: Windows XP SP2 Visual Studio 2003 .NET Framework v1.1.4322 SP1 Build File Contents ?xml version=1.0? project name=WFD default=build basedir=..\ descriptionKofax Standard Application NANT Build Script/description target name=build description=Compile project using Release configuration !-- TODO - Be sure to set the name of the solution file here -- echo message=Building Application/ solution solutionfile=wfd.sln configuration=Release /solution /target target name=clean delete verbose=true !-- TODO - Be sure to correct path to the release folder here -- fileset basedir=..\WFD\bin\release includes name=*.dll/ includes name=*.exe/ /fileset /delete /target /project Bug message: S:\WFD\WFD_NewUI\BuildC:\Tools\NAnt\build\net-1.1.win32\nant-0.84-debug\bin\nan t -buildfile:wfd_newui.build NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003) Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///S:/WFD/WFD_NewUI/Build/wfd_newui.build Target(s) specified: build build: [echo] Building Application [solution] Starting solution build. BUILD FAILED INTERNAL ERROR System.ArgumentNullException: Value cannot be null. Parameter name: path2 at System.IO.Path.Combine(String path1, String path2) at NAnt.VSNet.VcConfiguration.get_OutputPath() in c:\Tools\NAnt\src\NAnt.VSNe t\VcConfiguration.cs:line 118 at NAnt.VSNet.VcProject.GetOutputPath(String configuration) in c:\Tools\NAnt\ src\NAnt.VSNet\VcProject.cs:line 150 at NAnt.VSNet.Solution.GetDependenciesFromProjects() in c:\Tools\NAnt\src\NAn t.VSNet\Solution.cs:line 453 at NAnt.VSNet.Solution..ctor(String solutionFileName, ArrayList additionalPro jects, ArrayList referenceProjects, TempFileCollection tfc, SolutionTask solutio nTask, WebMapCollection webMappings, FileSet excludesProjects, String outputDir) in c:\Tools\NAnt\src\NAnt.VSNet\Solution.cs:line 115 at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in c:\Tools\NAnt\src\NAnt.VSNe t\Tasks\SolutionTask.cs:line 317 at NAnt.Core.Task.Execute() in c:\Tools\NAnt\src\NAnt.Core\Task.cs:line 151 at NAnt.Core.Target.Execute() in c:\Tools\NAnt\src\NAnt.Core\Target.cs:line 2 17 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in c:\Tools\NAnt\src\NAnt.Core\Project.cs:line 772 at NAnt.Core.Project.Execute() in c:\Tools\NAnt\src\NAnt.Core\Project.cs:line 734 at NAnt.Core.Project.Run() in c:\Tools\NAnt\src\NAnt.Core\Project.cs:line 797 Please send bug report to [EMAIL PROTECTED] Total time: 0.9 seconds. John Cornell Kofax Image Products Software Development Manager (949) 727-1733 Ext.336 http://www.kofax.com/
[nant-dev] [ nant-Bugs-1177737 ] nant task relative directory
Bugs item #1177737, was opened at 2005-04-06 08:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1177737group_id=31650 Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Submitted By: gabrandt (gabrandt) Assigned to: Nobody/Anonymous (nobody) Summary: nant task relative directory Initial Comment: we are updating our nant source from a nightly version (4/14/2004) to rc1 or rc2. there seems to be a behavior difference with nant tasks; when executing a build file located in a sub directory, the current directory remains that of the calling build file. in our current version, the relative location matched the executing build file location. is this a known change? it seems limiting that a called build file would have to be aware of it's relative position to it's caller in order to refer to any file resources. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1177737group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1177737 ] nant task relative directory
Bugs item #1177737, was opened at 2005-04-06 15:00
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1177737group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: gabrandt (gabrandt)
Assigned to: Nobody/Anonymous (nobody)
Summary: nant task relative directory
Initial Comment:
we are updating our nant source from a nightly version
(4/14/2004) to rc1 or rc2. there seems to be a behavior
difference with nant tasks; when executing a build file
located in a sub directory, the current directory remains
that of the calling build file. in our current version, the
relative location matched the executing build file
location. is this a known change? it seems limiting that
a called build file would have to be aware of it's relative
position to it's caller in order to refer to any file
resources.
--
Comment By: Gert Driesen (drieseng)
Date: 2005-04-06 15:09
Message:
Logged In: YES
user_id=707851
This is indeed a change that we made, but as this change
was not a change in behaviour compared to other officially
relased version of NAnt, we have not documented it as a
change.
In fact, the current directory is not set to the directory of the
calling build file, but the original working directory.
The reason for this change is that it allows more flexibility for
build files that want to perform tasks on the original working
directory. Also, there was no real need for changing the
current directory to the directory of the executing build file, as
all NAnt tasks will resolve files to the project base directory
anyway.
If necessary, a called build file can always determine its
directory using the expression support that was introduced in
NAnt 0.85.
For example:
echo message=project base directory=${project::get-base-
directory()} /
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=402868aid=1177737group_id=31650
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1178007 ] solution link error
Bugs item #1178007, was opened at 2005-04-06 12:00 Message generated for change (Comment added) made by rjontilt You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1178007group_id=31650 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ray Johnson (rjontilt) Assigned to: Nobody/Anonymous (nobody) Summary: solution link error Initial Comment: In one of our projects (we want to compile with the solution tage we are getting an error like this: [link] libeay32.lib [link] advapi32.lib [link] zlibd.lib [link] $(noinherit) ... [link] shell32.lib [link] ole32.lib [link] oleaut32.lib [link] uuid.lib [link] odbc32.lib [link] odbccp32.lib[link] [link] Starting 'link (@C:\DOCUME~1 \rayj\LOCALS~1\Temp\tmp7E9. tmp /INCREMENTAL:NO /SUBSYSTEM:CONSOLE /M ACHINE:X86)' in 'C:\src\devtrunk\FullT ilt\FT_Server\FTS_Casino' [link] LINK : fatal error LNK1181: cannot open input file '$(noinherit).obj' BUILD FAILED In our VS.Net project configuration Linker-Input- Additional Dependancies we have our list of additional libraries we want to include - this includes the $(NOINHERIT) macro. (This gets set if youhit the ... box and uncheck the Inherit from project defaults checkbox.) It appears that Nant is not honoring this macro (at least not in this context.) If this macro is set we also should not be attempting to link in many of the libraries listed above (those shown after where the $(noinherit) macro shows up). Ray -- Comment By: Ray Johnson (rjontilt) Date: 2005-04-06 12:01 Message: Logged In: YES user_id=1246077 BTW, this was a C++ project - if that makes a difference. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1178007group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAnt home page
The new home page doesn't have a link to the NantContrib page any more... -- Troy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
