[Mono-dev] Altering our build system.

Atsushi Eno atsushieno at veritas-vos-liberabit.com
Tue May 25 02:41:15 EDT 2010

- 1 won't be determined without the actually altered build system,
- 2 is just impossible (no "make install" alternative and we need it), and
- 3 in VS requires non-express versions as long as it depends on NUnit addin
   (and of course we can't migrate our tons of existing NUnit tests to 
something else)

this "migrate to VS" should be taken out of this core build change 
discussion IMO.

Atsushi Eno

On 2010/05/21 3:37, Jonathan Chambers wrote:
> I've been looking at a MSBuild based build for the class libs (based 
> upon Jonathan Pobst's MonkeyBuilder). To actually make the projects 
> usable in visual studio, they need to be one of a list of well known 
> project types. While MSBuild can handle an arbitrary .proj file with 
> arbitrary MSBuild tasks, to build inside VS you would need to use a 
> .csproj. Currently, I have a build basically working using a .proj 
> file with custom MSBuild tasks that mirror what MonkeyBuilder does 
> (which mirrors the auto* based build). csproj files could be used, but 
> it raises a few questions:
> 1. Can we build using either .Net compilers or mono compilers?
> 2. Is there the concept of make and make install (building class libs 
> versus installing them in some location)?
> 3. Running unit tests
> There are more issues, but this is already a bit unrelated to Miguel's 
> original post. The Windows build has recently gone downhill, so 
> hopefully any changes we make might make life better (and hopefully no 
> worse).
> Thanks,
> Jonathan
> On Thu, May 20, 2010 at 2:10 PM, Jonathan Pryor <jonpryor at vt.edu 
> <mailto:jonpryor at vt.edu>> wrote:
>     On Thu, 2010-05-20 at 12:52 -0400, Miguel de Icaza wrote:
>     >      I would like to move to a setup where by default we assume
>     we have
>     > a working mcs/runtime and we build the configured profiles
>     (defaulting
>     > to 2.0 and 4.0).
>     ...
>     >      A final wish-list item would be to split up the *core*
>     libraries
>     > from most of the extra libraries.  The moonlight team is using a
>     special
>     > process already to limit the number of assemblies built.
>     This would dovetail nicely with the idea of splitting up mcs into
>     smaller modules as part of the git migration; see:
>     http://www.mono-project.com/GitMigration
>     I would also suggest using xbuild to build the non-core libraries.
>      This
>     will make it easier for people who aren't using Unix to build the
>     libraries, as Visual Studio could then (hopefully) be used for
>     building,
>     thus avoiding the pain that is Cygwin for everything except the
>     runtime
>     and core libraries.
>      - Jon
>     _______________________________________________
>     Mono-devel-list mailing list
>     Mono-devel-list at lists.ximian.com
>     <mailto:Mono-devel-list at lists.ximian.com>
>     http://lists.ximian.com/mailman/listinfo/mono-devel-list
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list