[m-rev.] for review: documentation updates and fixes for MSVC port

Julien Fischer juliensf at csse.unimelb.edu.au
Mon Nov 7 22:54:50 AEDT 2011




On Mon, 7 Nov 2011, Paul Bone wrote:

> On Mon, Nov 07, 2011 at 03:18:45PM +1100, Julien Fischer wrote:
>>
>> For review by anyone.
>>
>> Branches: 11.07, main
>>
>> Improve and update documentation of the MSVC port.
>>
>> Add batch files for invoking mdb and mprof; avoid problem with mercury.bat.
>>
>> README.MS-VisualC:
>> 	Rewrite this file, it was very much out-of-date.
>> 	The major changes are:
>>
>> 	+ we now describe how to set up a Cygwin or MSYS shell
>>   	  with MSVC available.
>>
>> 	+ the source distribution now works with MSVC.
>>
>> 	+ a list of the limitations of the MSVC port has been added.
>>
>> 	+ a description of how to set up the compier so that it
>> 	  works from the Windows command prompt has been added.
>
> *compiler*

Fixed.

>> Index: README.MS-VisualC
>> ===================================================================
>> RCS file: /home/mercury/mercury1/repository/mercury/README.MS-VisualC,v
>> retrieving revision 1.8
>> diff -u -r1.8 README.MS-VisualC
>> --- README.MS-VisualC	7 Mar 2006 06:40:39 -0000	1.8
>> +++ README.MS-VisualC	7 Nov 2011 04:06:56 -0000
>
>> +
>> +The `--with-msvcrt' flag causes executables built with this install of Mercury
>> +to be linked with the MS Visual C runtime, instead of the standard libC
>> +runtime.
>> +
>> +On Cygwin, configure and mmake will do translation of Unix style paths, so you
>> +may specify the installation directory using either a Unix- or Window-style
>> +path.  On MSYS, you must use a Window-style path.
>>
>
> Maybe this is a dumb question from a non-windows guy.  But is the only
> difference the direction of the slashes?  ie \ for windows and / for Unix?  Do
> the unix style paths on a windows system include the drive letter?

Both Cygwin and MSYS map the driver letter onto their view of the file 
systems,  For MSYS, c: is simpley /c, for Cygwin it is /cygdrive/c.

>> -3. To build a version of the mercury compiler with MSVC++ instead of
>> -   gcc, remotely check out a fresh version of the compiler, eg.
>> +* Deep profiling, e.g. the *.profdeep grades, does not (currently) work
>> +  with MSVC.  (In principle, it should work if the clock tick metric is
>> +  disabled.)
>>
>
> *do not currently work* because grades is plural.  I could be wrong because
> this phrase is parenthetical.

Deep profiling is singular.

Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the reviews mailing list