hmm, well build.cmd works but build falls over on something to do with nunit, have shut down for the night now but will have a look at it tomorrow to see what's going wrong there. Thanks for the info.
2009/8/30 Jonathon Rossi <[email protected]> > From an OS perspective there shouldn't be anything different between > running "build" or "build.cmd". If you look at the contents of build.cmd > you'll see it uses NAnt from the SharedLibs directory so it is not using the > one on your path. > > On Sun, Aug 30, 2009 at 11:03 AM, DannyT <[email protected]> wrote: > >> Okay so after opening the 'How to build.txt' I followed the instruction >> and typed: >> >> > build >> >> into the command prompt whilst in the castle dir, however after going back >> to check this, I realise this seems to trigger nant to look for and execute >> 'default.build' as opposed to 'build.cmd' >> >> When I typed: >> >> > build.cmd >> >> everything built in a release folder and all is good. I'm using the latest >> nightly build of nant, not sure if that's a change in behaviour of nant or >> something strange I have going on? >> >> Dan >> >> 2009/8/30 Jonathon Rossi <[email protected]> >> >>> You shouldn't have to use the solution files. Our build server has had >>> no issues building the trunk and I just tried the build.cmd and it worked >>> with MK and Windsor dlls in the build directory. >>> >>> Can you provide more details on the error you are getting. If the >>> reference error is to do with NVelocity then you will probably need to >>> delete /Tools/NVelocity and update with externals. >>> >>> >>> On Sun, Aug 30, 2009 at 10:10 AM, DannyT <[email protected]>wrote: >>> >>>> >>>> I'm trying to build Castle from trunk as a learning exercise more than >>>> anything. After checking out the trunk I have successfully ran the >>>> build.cmd which created a build folder with all compiled assemblies. >>>> >>>> This didn't however contain castle.windsor. >>>> >>>> I _was_ able to open the Castle-all-vs2008.sln and build it windsor >>>> from visual studio and also able to build from InversionOfControl- >>>> vs2008.sln but I wasn't able to build using nant from the >>>> Castle.Windsor.Build file getting various reference issues. >>>> >>>> I then tried to run InversionOfControl.build thinking that might >>>> generate the needed assemblies but that failed with a nullreference >>>> error on the microkernal tests at which point I'm a little out of my >>>> depth. >>>> >>>> Like I said I could build windsor from VS so I essentially achieved >>>> what I set out to do (build from trunk) but I'd appreciate any >>>> indication as to what I'm doing wrong to be able to get it to build >>>> with Nant? >>>> >>>> Cheers, >>>> Dan >>>> >>>> >>>> >>> >>> >>> -- >>> Jono >>> >>> >>> >> >> >> -- >> http://danny-t.co.uk >> >> >> >> > > > -- > Jono > > > > -- http://danny-t.co.uk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
