[Mono-dev] Mono 126.96.36.199 Windows Installer Released
Francisco T. Martinez
martinf at mfconsulting.com
Sat Oct 1 10:08:49 EDT 2005
Wade Berrier wrote:
>On Fri, 2005-09-30 at 07:03 -0500, Francisco Martinez wrote:
>>Wade it shows all the hard work you have put into this. Good job!
>>Since some of the exe(s) are now in a different location, I will have to
>>adjust the tools like MonoLaunch and the Visual Studio .NET add-in
>>(vsprj2make). However, that is the way it should be :) I am now
>>officially the third party and it is my responsibility to adjust to the
>>direction that Novell is setting on the installer.
>Hi Paco, as noted in another message on the list, I didn't do any moving
>of the mono wrapper or the mono.exe. The make install set it up like
>that. Seems to be working fine though.
Correct. I was the one that always moved them from bin directory to the
lib directory. This I would do to keep only the shell scripts and batch
files in the bin directory and all exe(s) in the lib directory so that
they would reside with the unmanaged dll(s) that the build process
creates as a bi-product of its running.
Again, don't take this as me saying that there should be a move. I am
just saying that after more than a year of doing all the builds and the
post build integration testing I had things the way I did because it
seem to work best. However, all the recent buzz in the list over the
Windows installer probably translates to a lot more help from a lot more
qualified people and it will probably lead to the best automated and
reproducible build process -- that is a good thing!
A lot of the decisions I made in my build procedure were done so that I
could use the *NIX build process without any alteration while building
More information about the Mono-devel-list