Since NAnt is running out of the svn I this might be a .config issue.
However, I don't know where mono installs by default on linux, so it is
probably an agent issue.

2009/5/31 Roelof Blom <[email protected]>

> That's a build agent problem isn't it?
>
>
> 2009/5/31 Jonathon Rossi <[email protected]>
>
>> The Mono build still doesn't get off the ground:
>>
>>> *Mono 3.5 Profile (mono-3.5) is not installed, or not correctly
>>> configured. Framework directory '/usr/lib/mono/3.5' does not exist. *
>>>
>>
>> 2009/5/31 Roelof Blom <[email protected]>
>>
>>> Guess I should follow on you twitter :-)
>>>
>>> 2009/5/31 Jonathon Rossi <[email protected]>
>>>
>>> I was just about to start doing that :)
>>>>
>>>> Sorry for not owning up to my promise on twitter.
>>>>
>>>> 2009/5/31 Roelof Blom <[email protected]>
>>>>
>>>> Patrick,
>>>>>
>>>>> I've applied all your patches in r5728.
>>>>>
>>>>> -- Roelof.
>>>>>
>>>>> 2009/5/27 Patrick McEvoy <[email protected]>
>>>>>
>>>>>
>>>>>> I had a little look at both, I can imagine it was hairy!
>>>>>>
>>>>>> Also I have a few patching requests to make further progress with the
>>>>>> mono/linux TC agent.
>>>>>>
>>>>>> 1. gacutil permissions
>>>>>> Root access is required to add a assembly to the gac. Running the
>>>>>> build as root can't be the recommended way. Till I come up with a
>>>>>> better we need failonerror="false"
>>>>>> Other bits of the patch are optional as I have discovered that most
>>>>>> mono tools support arguments with either - or /
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/gacutil.diff
>>>>>>
>>>>>> 2. Case sensitivity
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/incorrect_case_on_bin_dir.diff
>>>>>>
>>>>>> 3. Explicitly reference System.Web.dll, System.Data.dll,
>>>>>> System.Configuration.dll
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/missing_system-data_ref.diff
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/missing_system-web_ref.diff
>>>>>>
>>>>>> 4. Adding set-mono-3.5-framework-configuration target and tweak for
>>>>>> svn revision capture
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/mono-3.5-target.diff
>>>>>>
>>>>>> 5. More issues with - or / as arguments for nunit, timeout is
>>>>>> important as some test assemblies currently stall with mono
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/nunit_commandline_options.diff
>>>>>>
>>>>>> 6. Mono bug, it's on my list to add to novell bugzilla :)
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/potential_mono_bug.diff
>>>>>>
>>>>>> 7. Mono can't build some test assemblies or NLog integration, for the
>>>>>> time being it's more beneficial for the community to ignore them under
>>>>>> mono, again it's high on my todo list to get them back in.
>>>>>> Patch:
>>>>>> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/remove_projects_with_references_to_win_only_assemblies.diff
>>>>>>
>>>>>> 8. Microsoft.Build.Engine problems...
>>>>>> Please comment out SharedLibs/build/NAnt/bin/NAnt.exe.config:1782,
>>>>>> afaik it's not used and this will only affect nant when targeting
>>>>>> mono-3.5
>>>>>>
>>>>>> Cheers :)
>>>>>>
>>>>>> On May 25, 11:18 pm, Jonathon Rossi <[email protected]> wrote:
>>>>>> > I assume you were looking Castle.NVelocity in the contrib
>>>>>> repository, not
>>>>>> > NVelocity in the main repository.
>>>>>> >
>>>>>> > I didn't think it was that hard to follow :). I did start it as a
>>>>>> rewrite
>>>>>> > but I had to add way too much stuff to support the strange cases
>>>>>> when you
>>>>>> > half type something, so it got pretty hairy.
>>>>>> >
>>>>>> > I do plan to rename that project, I was going to move it under the
>>>>>> CVSI
>>>>>> > project since it isn't of use outside an IDE, but can rename it to
>>>>>> some more
>>>>>> > IDE generic if you want to use it.
>>>>>> >
>>>>>> > 2009/5/26 Patrick McEvoy <[email protected]>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > > I spent a few hours looking around after you mentioned this,
>>>>>> including
>>>>>> > > looking at the NVelocity codebase... wow, that was hard to follow!
>>>>>> I
>>>>>> > > need to spend more time on it, but it makes sense to use the same
>>>>>> > > tools/parser if we can. I might even bite the bullet and start a
>>>>>> > > rewrite of NVelocity, be interesting to see how far I can get in a
>>>>>> few
>>>>>> > > days... :)
>>>>>> >
>>>>>> > > Cheers for the heads up.
>>>>>> >
>>>>>> > > On May 23, 5:55 pm, Jonathon Rossi <[email protected]> wrote:
>>>>>> > > > Have you considered using CVSI's NVelocity parser? It is
>>>>>> separate from
>>>>>> > > the
>>>>>> > > > Visual Studio stuff.
>>>>>> >
>>>>>> > >
>>>>>> http://using.castleproject.org/display/Contrib/Castle+Visual+Studio+I.
>>>>>> ..
>>>>>> >
>>>>>> > > > 2009/5/24 Patrick McEvoy <[email protected]>
>>>>>> >
>>>>>> > > > > That's a good idea! We can can hook it into TC too :)
>>>>>> >
>>>>>> > > > > Can someone sort me out with contrib svn access?
>>>>>> >
>>>>>> > > > > Cheers P
>>>>>> >
>>>>>> > > > > On May 23, 5:15 pm, Krzysztof Koźmic <
>>>>>> [email protected]>
>>>>>> > > > > wrote:
>>>>>> > > > > > Patrick,
>>>>>> >
>>>>>> > > > > > Regarding your monodevelop plugin.
>>>>>> > > > > > How about moving it to castle-contrib?
>>>>>> >
>>>>>> > > > > > Krzysztof
>>>>>> >
>>>>>> > > > > > Patrick McEvoy pisze:
>>>>>> >
>>>>>> > > > > > > Great to see there's others that are interested too!
>>>>>> >
>>>>>> > > > > > > I would be very happy to run and maintain a mono TC agent.
>>>>>> I'll
>>>>>> > > setup
>>>>>> > > > > > > an agent in the next few days with debian, mono-2.4.
>>>>>> >
>>>>>> > > > > > > Also just a heads up for debian/ubuntu users: Mirco Bauer
>>>>>> yesterday
>>>>>> > > > > > > uploaded mono-2.4 preview packages to his private repo.
>>>>>> We've found
>>>>>> > > > > > > mono-2.0 and mono-2.2 too buggy to run the castle stack,
>>>>>> so don't
>>>>>> > > > > > > bother trying on a stock jaunty install :)
>>>>>> > > > > > >http://go-mono.com/forums/#nabble-td23669501
>>>>>> >
>>>>>> > > > > > > And for anyone using MonoDevelop and MR we wrote a little
>>>>>> plugin,
>>>>>> > > it's
>>>>>> > > > > > > rough round the edges but works :)
>>>>>> > > > > > >http://code.google.com/p/monodevelop-castle/
>>>>>> >
>>>>>> > > > > > > There aren't that many MoMA issues these days, still a few
>>>>>> things
>>>>>> > > to
>>>>>> > > > > > > work out with DP2 tho.
>>>>>> >
>>>>>> > > > > > > Cheers P
>>>>>> >
>>>>>> > > > > > > On May 22, 4:43 pm, Markus Ewald <[email protected]>
>>>>>> wrote:
>>>>>> >
>>>>>> > > > > > >> On 5/22/2009 4:54 PM, Krzysztof Koźmic wrote:> Since Mono
>>>>>> runs on
>>>>>> > > > > Windows, we might set up a Mono build on a TS server.
>>>>>> >
>>>>>> > > > > > >>> Also, TS can run multiple build agents, if you Patrick
>>>>>> have a
>>>>>> > > spare
>>>>>> > > > > > >>> machine you could dedicate to running Linux + Mono
>>>>>> Castle bulids,
>>>>>> > > I
>>>>>> > > > > > >>> think this would be cool, and a great way to ensure good
>>>>>> > > > > compatibility +
>>>>>> > > > > > >>> immediate feedback if Windows OK update breaks Linux.
>>>>>> >
>>>>>> > > > > > >> A Linux + Mono box would definitely be useful since Win32
>>>>>> + Mono
>>>>>> > > still
>>>>>> > > > > > >> allows P/Invoke calls to Win32 API functions.
>>>>>> > > > > > >> Still, a Mono build in any form would go a long way in
>>>>>> making sure
>>>>>> > > it
>>>>>> > > > > at
>>>>>> > > > > > >> least compiles okay for us Mono users ;-)
>>>>>> >
>>>>>> > > > > > >>> Krzysztof
>>>>>> >
>>>>>> > > > > > >> -Markus-
>>>>>> >
>>>>>> > > > --
>>>>>> > > > Jono
>>>>>> >
>>>>>> > --
>>>>>> > Jono
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jono
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> Jono
>>
>>
>>
>
> >
>


-- 
Jono

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Development List" 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-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to