[Mono-dev] MSVC build of mono runtime
Jonathan Chambers
joncham at gmail.com
Wed May 14 16:08:11 EDT 2008
Hello,
I am trying to figure out the best way to integrate a MSVC compiler
built runtime into the mono build process. We currently maintain a .sln file
and a variety of .vcproj files in mono/msvc. Normally, I (and maybe a few
others in the world) maintain/build these inside of the Visual Studio IDE.
Normally, I do a full cygwin build (runtime/classlibs) followed by an MSVC
build of the runtime to get something usable. This is not too painful, but
is not automated in any way (and I rarely run tests with the VS built
runtime).
I am working on porting mono to Win64, and would like a more automated
way to build/test an MSVC runtime. gcc is not yet ported to Win64 so MSVC is
the only option to build the runtime (or only 'free' option I know of). I am
planning on building the runtime using the vcproj files that are already
somewhat maintained, rather than an additional set of makefiles. The vcproj
files can be built at the command line using the VCBuild tool in the Windows
SDK (something like 'VCBuild mono.sln Release|Win32').
I have two main questions. I would still like to use cygwin/make to
drive the overall build process. I just need to build the mono subdirectory
using the method mentioned above. Does anyone have any recommendations on
how to do this cleanly? The other question was, should this be a configure
option or a make target? Either something like './autogen.sh --with-msvc' if
during configuration, else 'make msvc' for make target. I started off trying
to make this a configuration option, but very little ended up changing in
the configuration as most of the differences are handled inside the MSVC
build process itself. I also have very little experience with auto-tools and
makefiles in general.
Any thoughts/advice would be appreciated.
Thanks,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080514/63976a76/attachment.html
More information about the Mono-devel-list
mailing list