You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5577 Reporter:@alainfrisch Status: closed (set by @xavierleroy on 2015-12-11T18:04:27Z) Resolution: not a bug Priority: normal Severity: minor OS: Windows Category: configure and build/install
Bug description
OCaml Makefile.nt fails upon 'make install' if the native compiler has not been built.
Under Unix, the Makefile tests for the presence of ocamlopt and calls the installopt target only if it exists. Is there a reason not to do the same under Windows?
The text was updated successfully, but these errors were encountered:
A simple reason: under Windows, ocamlopt is always built; under Unix, it's not always built because it's not supported on every platform that ocamlrun/ocamlc run on.
ocamlopt can always be built, but there could be cases where the user wants to build and install only the bytecode tools. I propose one of the following actions (by increasing order of preference):
Adapt Makefile.nt so as to force building the the native code version with the bytecode one (i.e. merge 'make opt' -- and also 'make opt.opt'? -- and 'make world').
Adapt README.win32 to indicate clearly that 'make opt' has to be executed before 'make install'. Or at least document the 'make installbyt' target.
Adapt Makefile.nt to do the same as under Unix, so as to allow more flexibility.
Original bug ID: 5577
Reporter: @alainfrisch
Status: closed (set by @xavierleroy on 2015-12-11T18:04:27Z)
Resolution: not a bug
Priority: normal
Severity: minor
OS: Windows
Category: configure and build/install
Bug description
OCaml Makefile.nt fails upon 'make install' if the native compiler has not been built.
Under Unix, the Makefile tests for the presence of ocamlopt and calls the installopt target only if it exists. Is there a reason not to do the same under Windows?
The text was updated successfully, but these errors were encountered: