Hey Charles, That function - which I consider to be internal - may indeed not be part of any official release. So in this case, you can only build NAnt with: * a "nightly" build (which hasn't been uploaded in quite a while due to scp/rsync issues with sourceforge) * a bootstrap of NAnt (though make/nmake) This last option is the one I'd recommend.
If that's ok for you, I'd like you to revert the changes to the build file that removed the use of nant::scan-probing-paths. Use of this function gives us more flexibility as to the actual location of some libraries. Sorry if I haven't been very responsive yet, but I hope to make up for this. Concerning your question about building on Linux: we actually have a linux box at our disposal through sponsorship by AOE media. I'll send you the details later (but don't hesitate to remind me if necessary). The reason why Gerry was not able to contact me, is because my corporate e-mail address (which I used in NAnt sources) changed after a merger. I'll update all sources when I find a idle spot. Regards Gert -----Original Message----- From: Charles Chan [mailto:cchan...@users.sourceforge.net] Sent: maandag 15 februari 2010 3:38 To: nant-developers@lists.sourceforge.net Subject: [nant-dev] NAnt status report [2010-02-14] FYI. Based on the information from Gerry, I spend the past week trying to 'build NAnt with NAnt'. The first order of business was to understand how the whole thing works. After diving around at the code (adding more comments along the way), I focused on NAnt.build... (Long story short) After I determined the main tasks in the .build file, I just kept running 'nant' (command). Repeated, I keep getting errors similar to the one below: Unknown function 'nant::scan-probing-paths'. Expression: ${nant::scan-probing-paths('nunit.framework.dll')} I could not find any information regarding this function on the website. Although I could see the function in the latest trunk, but trunk is not a (real) release. So in the end, to replicate an 'average' NAnt user, I decided to install the last official release (0.86-beta1) and use that as the basis for the build. After replacing all instances of 'scan-probing-paths' and fix it with the correct path, the 'build' target finally works. I verified the changes both locally and on TeamCity [http://teamcity.codebetter.com/project.html?projectId=project69] Next steps (prioritized): * The 'test' target also compiles and runs, but a few tests are failing. Need to investigate. * Look at nightly.xml to generate nightly releases. * Look at release.xml to generate official releases. * Generate additional docs / comments to help others in future. * (Request from Leszek) Investigate 1) Mono and 2) Linux configuration. I am thinking of openSuse Build Service, but needs more investigation? [https://build.opensuse.org/] Regards, Charles __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ---------------------------------------------------------------------------- -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2688 - Release Date: 02/14/10 20:35:00 ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
