[Mono-dev] [PATCH] Source list per profile
bmaurer at ximian.com
Tue Aug 16 11:11:44 EDT 2005
> Hi, Kornél.
> The .jvm.cs are part of the Java build that we are now doing from svn
> using make.
> The issue is not limited to the .jvm files but also to Mono sources
> (e.g. in System.Web) that are not part of the Java build. In System.Web
> we have about 30 Mono files that we don't compile in the Java build
> (because we don't support yet on the fly compilation of .aspx files and
> So in our case we have more files that belong to specific profiles or
> combinations of profiles.
> Personally, the issue here is the number of profiles and their
> complexity. The more profiles are used the more useful the proposed
> change is. If everyone believes that there are not going to be more
> profiles then the Java profile then there is less incentive to change
> anything - the current solution of ifdefs is still usable.
I don't see anyone adding another profile other than NET_2_1 or whatever.
What if there was a hack where blah.jvm.cs files are only compiled for the
jvm target and blah.cs is not compiled in the jvm target if blah.jvm.cs
That way the sources file stays the same (allowing us to echo FILENAME >
blah.sources and use sort | uniq).
More information about the Mono-devel-list