[Mono-dev] Repeat builds of core assemblies

[Rafael Teixeira]

Why don't we extend mcs to twist netmodules compilation into multi-assembly
compilation?

See http://msdn.microsoft.com/en-us/library/226t7yxe(v=vs.110).aspx

So that a line like below would work?

mcs /out:System.dll System/System.Collections.Generic/Queue.cs ...
/out:System.Xml.dll System.XML/System.Xml/XmlAttribute.cs ...


Then we would have a single pass on the build for building this troika.
For me it surely looks like a more sensible solution, aside from probably
eating a lot more memory for this compilation. :)

Another alternative would be to compile to netmodules with mcs and extend
Mono's al into converting them into multiple assemblies instead of a
multiple-file single assembly, code changes would be similar to the changes
in mcs, but multiple assembly metadata handling in the command line would
probably be more messy...


Just my crazy two cents...

Rafael Teixeira
O..:.)oooo


On Tue, Apr 22, 2014 at 11:16 PM, Miguel de Icaza <miguel at xamarin.com>wrote:

> how are you fitting msbuild in the build process? Just to confirm if you
>> using the generation of csharp project files and solutions for visual
>> studio?
>
>
> Yes, continuing the work on mono/msvs/scripts/genproj.cs
>
> There are already a few issues solved, but ran into this broken build
> setup, and quickly realized that we had this hack on the Makefiles which is
> why it works at all.
>
> There is quite some work left to be done for genproj.cs, but this is
> something that would benefit both.
>
> Miguel
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140423/f2a10b99/attachment.html>