Since we don't support .NET 2.0 in Castle anymore (except Core+DP2 which
have no 3rd party dependencies). Is there any reason for keeping them all
separate?

My proposal is not to separate 2.0/3.5 binaries until we get to .NET 4.0,
where we may have to because it has a different runtime.

This is an example of what I am going to start doing. I'd like to hear your
thoughts.

/SharedLibs/NHibernate.dll
/SharedLibs/Boo.Lang.dll

/SharedLibs/net/log4net.dll
/SharedLibs/net/Rhino.Mocks.CPP.Interfaces.dll
/SharedLibs/net/NUnitLite.Silverlight.dll
/SharedLibs/net/NHibernate.Linq.dll

/SharedLibs/mono/log4net.dll

On Thu, Jun 4, 2009 at 1:06 AM, Patrick McEvoy <[email protected]>wrote:

>
> There's also a problem with the nunit detection, with mono it was
> looking for nunit-console2, however since the mono-2.0 transition it's
> been renamed back to nunit-console. Another symbolic link fixed this,
> see common.xml:314 if you wanna fix it.
>
> There is no need to separate mono/net assemblies now and I don't see
> why that would change. I can rewrite the nant scripts to just use
> these paths SharedLibs/2.0, SharedLibs/3.5? Would this be welcomed? Or
> for the time being (and minimal fiction) can one of you just replicate
> SharedLibs/net -> SharedLibs/mono and apply the patch below...
>
>
> https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/common-xml-sharedlibs.diff
>
> On Jun 3, 2:40 pm, Roelof Blom <[email protected]> wrote:
> > Agreeing again with Jono: It would make more sense to let the Mono build
> use
> > the same assemblies as the Windows build, and copy any mono-specific
> > assemblies from the SharedLibs\mono directories.
> >
> > -- Roelof.
> >
> > On Wed, Jun 3, 2009 at 2:35 PM, Jonathon Rossi <[email protected]>
> wrote:
> > > There are files in /SharedLibs/mono that aren't even in
> /SharedLibs/net.
> >
> > > Do you really need to make an exact copy from net into mono, it seems a
> > > little redundant.
> >
> > > On Wed, Jun 3, 2009 at 10:28 PM, Patrick McEvoy <
> [email protected]>wrote:
> >
> > >> Cool, TC is getting a lot further, still need SharedLibs/mono/2.0
> > >> updating with all libs from SharedLibs/net/* :)
> >
> > >> On Jun 3, 11:09 am, Roelof Blom <[email protected]> wrote:
> > >> > I've applied both mono-nant-tweaks2.diff and
> > >> remove-ar-linq-on-mono.diff,
> > >> > let's see how it goes.
> >
> > >> > I tend to agree with Jonathon that we need a working
> NAnt.exe.config, so
> > >> > other people can easily build Castle on Mono.
> >
> > >> > -- Roelof.
> >
> > >> > On Wed, Jun 3, 2009 at 5:31 AM, Jonathon Rossi <[email protected]>
> > >> wrote:
> > >> > > The build looks like it is going good now. We just need to work on
> > >> fixing
> > >> > > things so that they all build and run on mono.
> >
> > >> > > So that other people can build on linux fairly easily, I think it
> > >> would be
> > >> > > better to modify the NAnt.exe.config.
> >
> > >> > > On Wed, Jun 3, 2009 at 10:14 AM, Patrick McEvoy <
> > >> [email protected]>wrote:
> >
> > >> > >> FYI... Packaging nant/nunit may be helpful with windows however
> not
> > >> so
> > >> > >> with linux. Since most distros will modified the mono install to
> a
> > >> > >> certain extent (and this is likely to include paths) the castle
> > >> > >> shipped NAnt.exe.config is referencing paths that don't exist. I
> > >> > >> assure you mono is installed exactly as it should be using the
> most
> > >> > >> update mono packages available from debian-cli team. So either I
> hack
> > >> > >> my install (I have done this), we hack the NAnt.exe.config or
> install
> > >> > >> & use nant from the packages. Unfortunately nant-0.85 is highest
> > >> > >> version available and 0.86beta is required for mono-3.5 target.
>  So
> > >> > >> the last option (which is obviously the best) isn't available and
> > >> NAnt
> > >> > >> does not play nice installing from source on linux.
> Linux/Mono/Castle
> > >> > >> is going to be a bumpy ride for a little while longer. However I
> do
> > >> > >> think Castle CI on mono/linux will help grow the team to tackle
> these
> > >> > >> simple yet time consuming issues for the benefit of the whole
> > >> > >> community.
> >
> > >> > >> On Jun 2, 10:43 am, Roelof Blom <[email protected]> wrote:
> > >> > >> > That patch was already applied, the build log quite clearly
> states
> > >> > >> what's
> > >> > >> > the problem:
> >
> > >>http://www.castleproject.org:8090/viewLog.html?tab=buildLog&buildType.
> ..
> >
> > >> > >> > On Sun, May 31, 2009 at 8:22 PM, Patrick McEvoy <
> > >> > >> [email protected]>wrote:
> >
> > >> > >> > > It needs this...
> >
> > >>https://qmtech.svn.beanstalkapp.com/castleproject_mono/trunk/patches/.
> > >> > >> ..
> >
> > >> > >> > > And something like this doing and committing...
> >
> > >> > >> > > cp SharedLibs/net/2.0/*.dll SharedLibs/mono/2.0
> > >> > >> > > cp SharedLibs/net/3.5/*.dll SharedLibs/mono/2.0
> > >> > >> > > cp SharedLibs/net/*.dll SharedLibs/mono/2.0
> >
> > >> > >> > > And also ar linq won't build because of NH.Linq requires
> > >> > >> > > System.Data.Services, patch coming real soon...
> >
> > >> > >> > > On May 31, 6:42 pm, Roelof Blom <[email protected]>
> wrote:
> > >> > >> > > > Patrick,
> >
> > >> > >> > > > The build keeps failing on Mono, can you verify that Mono
> is
> > >> > >> correctly
> > >> > >> > > > installed?
> >
> > >> > >> > > > -- Roelof
> >
> > >> > >> > > > On Sun, May 31, 2009 at 7:38 PM, <[email protected]>
> > >> wrote:
> > >> > >> > > > > Build Castle::Trunk - Debug (Mono) #6 failed
> > >> > >> > > > > Agent: Mono Linux
> > >> > >> > > > > Build results:
> >
> > >> > >>
> http://www.castleproject.org:8090/viewLog.html?buildId=79&buildTypeId
> > >> .
> > >> > >> > > ..
> >
> > >> > >> > > > > Changes included (1 change)
> > >> > >> > > > > ====================================================
> > >> > >> > > > > Change 5730 by roelofb (1 file):
> > >> > >> > > > > Another tweak for the Mono build agent
> >
> > >> > >> > > > > see more information about changed files:
> >
> > >> > >>
> http://www.castleproject.org:8090/viewLog.html?tab=buildChangesDiv&bu
> > >> .
> > >> > >> > > ..
> >
> > >>
> ============================================================================
> > >> > >> > > > > Configure email notifications:
> >
> > >> > >>
> http://www.castleproject.org:8090/profile.html?init=1#notifications
> >
> > >> > > --
> > >> > > 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