Makefile? I would venture to say that a NAnt or MSBuild file would be more useful.
----- Original Message ---- From: László Monda <l...@monda.hu> To: lucene-net-user@incubator.apache.org Sent: Tuesday, February 17, 2009 7:59:49 PM Subject: Re: Building Lucene.Net from SVN Seems like someone in the community has just made a make script - me. :) I've attached the Makefile. Your advice of using the .csproj file is correct, it works this way. Indexing is blazingly fast with the SVN build just as you mentioned. Is there anyone who is willing and authorized to merge my Makefile to the SVN trunk or should I post it to the developer list? I'd like to encourage the developers to tag all future releases and upload the DLLs to the release directory. By providing named releases you could strenghten the trust toward Lucene.Net. (I don't know about you, but I don't trust SVN builds and would prefer official builds. It's also more convenient.) On Tue, Feb 17, 2009 at 10:18 PM, Laimonas Simutis <lai...@gmail.com> wrote: > On Tue, Feb 17, 2009 at 2:35 PM, Digy <digyd...@gmail.com> wrote: >> Building a project does not mean just compiling the .cs files in all >> folders. There may be files excluded from the project but kept for some >> historical purposes, some files can be used as an embedded resource + there >> may exists some pre/post build actions to be done etc. >> >> So, There is a point in using a development-tool or a make-utility if you >> don't know what to do exactly. > > Totally agree. And I don't think being able to compile using mono but > on windows is sufficient. Some people would never want to involve > windows in the build process and would like to do it all on *nix > environment. > > Maybe someone in the community already has make scripts for doing > this, if not, we should start looking into it. > > > Laimis > > >> >> [snip]
