[Mono-list] Is nant being used by mono ?
Fri, 16 Aug 2002 04:19:51 -0700
Okay, will do. What's the best way to do this with cvs? I tried doing
'cvs update -r' to the previous version and it gets the older version
but cvs diff doesn't show any changes. Any ideas?
I've written a simple tinderbox script, but I'm stuck on a key testing
phase: I can't get a successful build :(
> -----Original Message-----
> From: Paolo Molaro [mailto:firstname.lastname@example.org]
> Sent: Friday, August 16, 2002 3:35 AM
> To: mono-list
> Subject: Re: [Mono-list] Is nant being used by mono ?
> On 08/15/02 Piers Haken wrote:
> > The main reason I did the rules thing was so we didn't have to
> > maintain the rather cumbersome lists of source files, which
> as far as
> > I could tell were becoming out-of-date quite frequently since not
> > everyone adding files is building on linux.
> Yes, that is a issue, but using *.cs is like saying: compile
> some random files... A tinderbox system can help the building
> issue (though everyone should try to test compile with the
> mono runtime anyway, before committing).
> > SOURCES_CMD=find . \
> > \( -false $(SOURCES_INCLUDE:%=-o -path '%') \) -a \
> > - ! \( -false $(SOURCES_EXCLUDE:%=-o -path '%') \)
> > + ! \( -false $(SOURCES_EXCLUDE:%=-o -path '%') \) -a \
> BTW, juli mentioned -false is not available in all the find
> implementations, so your changes broke the build on BSD
> systems, for example.
> > On the other hand, it would also be simple to back out the
> whole lot
> > and go back to the lists... I just see them being more trouble than
> > they're worth.
> We prefer to explicitly list the files that need to be
> compiled, so we want to go back to the lists: can you back
> out your changes?
> email@example.com debian/rules
> firstname.lastname@example.org Monkeys do it better
> Mono-list maillist - Monoemail@example.com
> http://lists.ximian.com/mailman/listinfo/mono-> list