> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant- > [EMAIL PROTECTED] On Behalf Of Curt Arnold > Sent: zaterdag 17 februari 2007 18:59 > To: nant-developers@lists.sourceforge.net > Subject: [nant-dev] NAnt on Gump, NAnt on Mac OS/X > > This is a continuation of a thread on general@gump.apache.org: http:// > mail-archives.apache.org/mod_mbox/gump-general/200702.mbox/% > [EMAIL PROTECTED] > > > On Feb 17, 2007, at 12:43 AM, Gert Driesen wrote: > > > > > >> -----Original Message----- > >> From: Curt Arnold [mailto:[EMAIL PROTECTED] > >> Sent: zaterdag 17 februari 2007 6:20 > >> To: Gump code and data > >> Subject: Re: Issue building NAnt > >> > >> > >> On Feb 16, 2007, at 7:09 PM, Curt Arnold wrote: > >>> However, if you try to do "nant" or "nant test", you will get a > >>> failure that <exec> doesn't support the managed attribute. It > >>> appears that the build file for NAnt requires features that are not > >>> in NAnt 0.85. Removing the managed="true" replaces that error with > >>> another when it tries to run the generated nant.exe as a Mac OS/X > >>> executable. > >>> > >>> > >> > >> Changing managed="true" to useruntimeengine="true" will let the > units > >> test pass. I'd suggest using the old name so that you can build the > >> next release of NAnt with the current release of NAnt and make the > >> switch after the next release. Basically undo this commit: http:// > >> nant.cvs.sourceforge.net/nant/nant/NAnt.build?r1=1.236&r2=1.237 > > > > I wonder if Ant also does not require to bootstrap the version of > > Ant that > > you want to build. > > > > I don't think it's necessary to ensure NAnt can be built using a > > previous > > release, if such a bootstrap procedure is in place. > > > > Nevertheless, I have no problem undoing that commit. It's your call. > > > > Gert > > > I don't know Ant's policy on this. I think switching back to > useruntimeengine is beneficial particular since Mono is bundled with > 0.85.
Ok, I'll do this tomorrow. > I was trying to scramble to get something building on Mac OS/X and my > first attempt using make failed with: > > > BUILD FAILED > > > > The current runtime framework 'mono-2.0' is not correctly > > configured in the NAnt configuration file. > > Unable to locate 'mono' module using pkg-config. Download the > > Mono development packages from http://www.mono- > project.com/downloads/. > > > > For more information regarding the cause of the build failure, run > > the build again in debug mode. > > Which stopped me cold. Then I found that NAnt 0.85 was installed > with Mono and then tried using NAnt 0.85 to build NAnt which lead to > me the install bug (See http://www.bleepsoft.com/tyler/index.php? > itemid=82 and http://bugzilla.ximian.com/show_bug.cgi?id=79671) and > then the use of managed="true". > > On reflection, the make build on Mac OS/X is suffering from the same > problem that affected the Mono install. NAnt is unable to find the > pkgconfig without PKG_CONFIG_PATH being explicitly set. If I did: > > setenv PKG_CONFIG_PATH /Library/Frameworks/Mono.framework/Versions/ > Current/lib/pkgconfig > > before running make, it still failed but differently. It might be > helpful to mention setting PKG_CONFIG_PATH in README.txt and possibly > change the message that is given since the prescribed remedy does not > fix them problem. Maybe a link to a page describing how to > troubleshoot pkg-config problems would be better. Ok, I'll look into this. > After setting PKG_CONFIG_PATH, the build fails like so: > > Buildfile: file:///Users/curta/ls-svn/nant/src/NAnt.Core/ > NAnt.Core.build > Target framework: Mono 2.0 Profile > Target(s) specified: build > > > build: > > [csc] Compiling 158 files to '/Users/curta/ls-svn/ > nant/build/mono-2.0.unix/nant-0.86-debug/bin/NAnt.Core.dll'. > [resgen] Mono Resource Generator version > 0.1 > [resgen] Usage: > [resgen] resgen source.ext [dest.ext] > [resgen] resgen /compile source.ext > [,dest.resources] [...] > [resgen] > [resgen] Convert a resource file from one > format to another. > [resgen] The currently supported formats > are: '.txt' '.resources' '.resx' '.po'. > [resgen] If the destination file is not > specified, source.resources will be used. > [resgen] The /compile option takes a list > of .resX or .txt files to convert to > [resgen] .resources files in one bulk > operation, replacing .ext with .resources for > [resgen] the output file name. > [resgen] > > BUILD FAILED > > External Program Failed: /Library/Frameworks/ > Mono.framework/Versions/1.2.3.1/lib/mono/2.0/resgen.exe (return code > was 1) This should now be fixed in CVS (since earlier today). I had submitted a patch for Mono, but it didn't get approved in time for the 1.2.3.1 release. I've committed a check to NAnt CVS to only enable usage of the resgen /usesourcepath option on Mono 1.2.4 or higher. Gert ------------------------------------------------------------------------- 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
