RE: [Caml-list] beta-test of OCaml 3.10.0: compiling on Windows,trying the new Camlp4

RE: [Caml-list] beta-test of OCaml 3.10.0: compiling on Windows,trying the new Camlp4

[EL CHAAR Rabih SGAM/AI/SAM]

[-- Attachment #1: Type: text/plain, Size: 4242 bytes --]

Just a comment concerning the microsoft build.

There is a batch called vcvars32.bat which handles setting correctly the VC2005 environment.

Calling it (in cygwin.bat) should handle all your problems for compilation.

 

For the rest of your questions, I can't be of any assistance.

 

Sincerely,

Rabih

 

________________________________

De : caml-list-bounces@yquem.inria.fr [mailto:caml-list-bounces@yquem.inria.fr] De la part de Matthieu Wipliez
Envoyé : vendredi 23 mars 2007 18:28
À : Caml List
Objet : [Caml-list] beta-test of OCaml 3.10.0: compiling on Windows,trying the new Camlp4

 

Hello,

I compiled OCaml 3.10.0 on Windows XP SP2 using Cygwin and Microsoft Visual Studio 2005.
Surprisingly, this did not go as smoothly as I thought. Hence I would like to share my experience:

1) the directory where the MSVC compiler, linker, and other tools are installed must be in the path : C:\Program Files\Microsoft Visual Studio 8\VC\bin
2) some tools (at least the compiler and linker) apparently need a DLL (mspdb80.dll), so one has to add "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE" to the path
3) under Cygwin, I had a clash between the linker (link) and the link command (link (GNU coreutils) 5.97). For everything to work, I had to remove the link command from Cygwin (renamed the link.exe file).
4) the compiler needs the INCLUDE variable to be defined with the MSVC include path (as well as Tcl's, but this is specified in the doc)
C:\Program Files\Microsoft Visual Studio 8\VC\include;C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include;C:\Tcl\include
5) for the linker, the variable is called LIB, and must contain:
C:\Program Files\Microsoft Visual Studio 8\VC\lib;C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib;C:\Tcl\lib

I would suggest to update the documentation (README.win32 file) by adding precisions concerning the INCLUDE, LIB and PATH variables, as well as the "link" command problem.

In addition, it seems that compilation can fail if OCAMLLIB is defined (complains about a .cmi in $OCAMLLIB not being up to date).


After compilation/installation, I tested this new version, compiling with "ocamlc.opt -pp camlp4o.opt". Is it still the right way to preprocess with Camlp4 ? Anyway, here's what I obtain:
  - in a class, "method private virtual" is not accepted anymore, the order has to be "method virtual private".
  - assert MySet.is_empty set; is not accepted anymore either, I have to add brackets: assert (MySet.is_empty set);
  - compiling a file containing this kind of comment (* <<<< COMMENT *) fails with "Quotation not terminated".
  - in a .mli, declaring an empty module ABC, with "module type ABC" does not work (but does without preprocessing).

I used the version from http://caml.inria.fr/pub/distrib/ocaml-3.10/ocaml-3.10.0+beta.tar.gz, so maybe some things have been corrected since.


Matthieu

 

________________________________

Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses <http://fr.rd.yahoo.com/evt=42054/*http:/fr.answers.yahoo.com> .

Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. 
Toute utilisation ou diffusion non autorisee est interdite. 
Tout message electronique est susceptible d'alteration. 
Societe Generale Asset Management et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. 
  
Decouvrez l'offre et les services de Societe Generale Asset Management sur le site www.sgam.fr 
  
                                ******** 
  
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration. 
Neither Societe Generale Asset Management nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. 
 
Find out more about Societe Generale Asset Management's proposal on www.sgam.com

[-- Attachment #2: Type: text/html, Size: 8850 bytes --]

Re: [Caml-list] beta-test of OCaml 3.10.0: compiling on Windows, trying the new Camlp4

[Jean-Marc EBER]

Hi all,

I also checked a few days ago the compilation/bootstrap of "ocaml3.10 beta" with 
vs2005 under cygwin (32 bits only):

We don't use CamlP4, so I can't comment on that.

Most of the points mentionned by Matthieu seem to be "vs2005 installation" 
related (you could install your IDE and/or compiler somewhere else) and, as 
Rabih said, can be installed by a batch file.

- I didn't have any problem with the "ocaml-3.10.0+beta.tar.gz" file. Everything 
worked out of the box.

- If you try a compilation on a version obtained by "cvs -d .... checkout -r 
release310 ocaml":

. a bootstrap problem has been fixed yesterday (a binary file was not marked as 
binary in the cvs)
. under "some" cygwin installations (don't ask me why!), the file ./VERSION 
obtained from cvs checkout has corrupted end of line caracters. So you must edit 
it to put it into "windows" text form.

But then, everything worked correctly.

BTW: the "mingw version" also compiled fine.

Jean-Marc


EL CHAAR Rabih SGAM/AI/SAM wrote:

> Just a comment concerning the microsoft build.
> 
> There is a batch called vcvars32.bat which handles setting correctly the 
> VC2005 environment.
> 
> Calling it (in cygwin.bat) should handle all your problems for compilation.
> 
>  
> 
> For the rest of your questions, I can’t be of any assistance.
> 
>  
> 
> Sincerely,
> 
> Rabih
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *De :* caml-list-bounces@yquem.inria.fr 
> [mailto:caml-list-bounces@yquem.inria.fr] *De la part de* Matthieu Wipliez
> *Envoyé :* vendredi 23 mars 2007 18:28
> *À :* Caml List
> *Objet :* [Caml-list] beta-test of OCaml 3.10.0: compiling on 
> Windows,trying the new Camlp4
> 
>  
> 
> Hello,
> 
> I compiled OCaml 3.10.0 on Windows XP SP2 using Cygwin and Microsoft 
> Visual Studio 2005.
> Surprisingly, this did not go as smoothly as I thought. Hence I would 
> like to share my experience:
> 
> 1) the directory where the MSVC compiler, linker, and other tools are 
> installed must be in the path : C:\Program Files\Microsoft Visual Studio 
> 8\VC\bin
> 2) some tools (at least the compiler and linker) apparently need a DLL 
> (mspdb80.dll), so one has to add "C:\Program Files\Microsoft Visual 
> Studio 8\Common7\IDE" to the path
> 3) under Cygwin, I had a clash between the linker (link) and the link 
> command (link (GNU coreutils) 5.97). For everything to work, I had to 
> remove the link command from Cygwin (renamed the link.exe file).
> 4) the compiler needs the INCLUDE variable to be defined with the MSVC 
> include path (as well as Tcl's, but this is specified in the doc)
> C:\Program Files\Microsoft Visual Studio 8\VC\include;C:\Program 
> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include;C:\Tcl\include
> 5) for the linker, the variable is called LIB, and must contain:
> C:\Program Files\Microsoft Visual Studio 8\VC\lib;C:\Program 
> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib;C:\Tcl\lib
> 
> I would suggest to update the documentation (README.win32 file) by 
> adding precisions concerning the INCLUDE, LIB and PATH variables, as 
> well as the "link" command problem.
> 
> In addition, it seems that compilation can fail if OCAMLLIB is defined 
> (complains about a .cmi in $OCAMLLIB not being up to date).
> 
> 
> After compilation/installation, I tested this new version, compiling 
> with "ocamlc.opt -pp camlp4o.opt". Is it still the right way to 
> preprocess with Camlp4 ? Anyway, here's what I obtain:
>   - in a class, "method private virtual" is not accepted anymore, the 
> order has to be "method virtual private".
>   - assert MySet.is_empty set; is not accepted anymore either, I have to 
> add brackets: assert (MySet.is_empty set);
>   - compiling a file containing this kind of comment (* <<<< COMMENT *) 
> fails with "Quotation not terminated".
>   - in a .mli, declaring an empty module ABC, with "module type ABC" 
> does not work (but does without preprocessing).
> 
> I used the version from 
> http://caml.inria.fr/pub/distrib/ocaml-3.10/ocaml-3.10.0+beta.tar.gz, so 
> maybe some things have been corrected since.
> 
> 
> Matthieu
> 
>  
> 
> ------------------------------------------------------------------------
> 
> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos 
> questions ! Profitez des connaissances, des opinions et des expériences 
> des internautes sur Yahoo! Questions/Réponses 
> <http://fr.rd.yahoo.com/evt=42054/*http:/fr.answers.yahoo.com>.
> 
> Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. 
> Toute utilisation ou diffusion non autorisee est interdite. 
> Tout message electronique est susceptible d'alteration. 
> Societe Generale Asset Management et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. 
>   
> Decouvrez l'offre et les services de Societe Generale Asset Management sur le site www.sgam.fr 
>   
>                                 ******** 
>   
> This message and any attachments (the "message") are confidential and intended solely for the addressees. 
> Any unauthorised use or dissemination is prohibited. 
> E-mails are susceptible to alteration. 
> Neither Societe Generale Asset Management nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. 
>  
> Find out more about Societe Generale Asset Management's proposal on www.sgam.com
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

Re: [Caml-list] beta-test of OCaml 3.10.0: compiling on Windows, trying the new Camlp4

[Nicolas Pouillard]

On 3/23/07, Matthieu Wipliez <mwipliez@yahoo.fr> wrote:
>
> Hello,
Hello,

[...]

>
> After compilation/installation, I tested this new version, compiling with
> "ocamlc.opt -pp camlp4o.opt". Is it still the right way to preprocess with
> Camlp4 ?

If you want to use the original syntax, yes.

> Anyway, here's what I obtain:
>   - in a class, "method private virtual" is not accepted anymore, the order
> has to be "method virtual private".

It was a bug in the new camlp4 (fixed in CVS).

>   - assert MySet.is_empty set; is not accepted anymore either, I have to add
> brackets: assert (MySet.is_empty set);

Assuming you want the original syntax, then it was a bug to accept it
since ocamlc also requires parentheses.

>   - compiling a file containing this kind of comment (* <<<< COMMENT *)
> fails with "Quotation not terminated".

That's not a bug that's a feature like strings, quotations are read by
the lexer.
However if you don't use quotation in your source file you can give
the  -no_quot option to camlp4.

>   - in a .mli, declaring an empty module ABC, with "module type ABC" does
> not work (but does without preprocessing).

I missed that feature (now fixed in CVS too).

> I used the version from
> http://caml.inria.fr/pub/distrib/ocaml-3.10/ocaml-3.10.0+beta.tar.gz,
> so maybe some things have been corrected since.

Yes, try the CVS (-r release310).

The new changes will be propagated in a few hours.

-- 
Nicolas Pouillard