Re: Task/planning for 0.87 release
Ryan Boggs <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nant.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, This is to address that lag time issue that I have been seeing on my Linux boxes. Attached is a diff that gets around the issue while I dig further. THIS IS NO MEANS A FINAL SOLUTION. It's only a band-aid until I can properly create a proper fix. One of my problems that I am having with this issue is that I am flying blind. No matter what I do or how many echos/console writes I put in, I can't see any output. I think my next step is using the mono debugger or gdb. Anyone have any tips on these tools that I can use or where else I should be looking? Thanks, Ryan On Sat, Mar 6, 2010 at 2:10 PM, Ryan Boggs <[email protected]> wrote: > Hi, > > On Sat, Mar 6, 2010 at 1:48 PM, Dominik Guder <[email protected]> wrote: >> Am 06.03.2010 22:38, schrieb Ryan Boggs: >>> Hey Gert, >>> >>> Question regarding the NAnt.build file, in particular the userdoc >>> target. Could you help me understand why the "self-userdoc" target is >>> being called via the exec program task rather than calling it >>> internally? I know there must be a reason for this approach but I am >>> having difficulty understanding. >>> >>> Thanks in advance, >>> Ryan >>> >> >> Hi Ryan, >> >> you should look who is calling Nant.build file. >> Basically it is "bootstrap\nant.exe" or any other nant.exe to build the >> new "nant.exe". And self-doc should use the newly generated nant.exe >> If it was called internally then the "bootstrap\nant.exe" will be >> documented not the new one. >> > Ah, makes complete sense. Thanks for pointing that out to me. > >> hth >> >> Dominik >> >> >> >> -- >> The answer to the great question of life, >> the universe and everything is 42 (Douglas Adams) >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> nant-developers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/nant-developers >> > > > > -- > Thanks, > Ryan > -- Thanks, Ryan ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ nant-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-developers
mono_ndoc_bandaid.diff
(application/octet-stream, 911 B)
Index: NAnt.build
===================================================================
RCS file: /cvsroot/nant/nant/NAnt.build,v
retrieving revision 1.258
diff -u -r1.258 NAnt.build
--- NAnt.build 14 Feb 2010 06:17:21 -0000 1.258
+++ NAnt.build 7 Mar 2010 01:59:18 -0000
@@ -821,7 +821,8 @@
<target name="install" depends="install-windows, install-linux" />
- <target name="install-windows" depends="userdoc" if="${platform::is-win32()}">
+ <target name="install-windows" depends="build" if="${platform::is-windows()}">
+ <call target="userdoc" unless="${string::contains(string::to-lower(framework::get-runtime-framework()), 'mono')}" />
<!-- install to program files directory by default -->
<property name="install.prefix" value="${environment::get-folder-path('ProgramFiles')}" />
<if test="${property::exists('prefix') and string::get-length(prefix) != 0}">