Databases
StackOverflow2013
Postsdbo
POz3 ocaml binding not working (windows 7)
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POz3 ocaml binding not working (windows 7)
    text
    copied!<p>I am not getting the z3 ocaml binding working on windows 7. Here is the process I followed.</p> <ol> <li>Installed Objective Caml version 3.11.0 (Microsoft toolchain)</li> <li>Installed camlidl-1.05 (built it using Microsoft Visual Studio 2008 + cygwin)</li> <li>Installed z3-3.0</li> <li>Built z3 ocaml binding by running "build.cmd".The build was successful.</li> <li>Copied the files generated by "build.cmd" from z3/ocaml to ObjectiveCaml/lib</li> <li><p>Launched ocaml interactive and loaded "z3.cma"</p> <pre><code># #load "z3.cma";; Characters -1--1: #load "z3.cma";; Error: The external function `get_theory_callbacks' is not available # Z3.mk_context;; Characters -1--1: Z3.mk_context;; Error: The external function `camlidl_z3_Z3_mk_context' is not available </code></pre></li> </ol> <p>Can someone please give me some hints?</p> <p>EDIT 1: <strong>Building the example in "Z3-3.0\examples\ocaml":</strong></p> <p>Excerpt from <em>build.cmd</em></p> <pre><code>set XCFLAGS=/nologo /MT /DWIN32 ocamlopt -ccopt "%XCFLAGS%" -o test_mlapi.exe -I ..\..\ocaml ole32.lib %OCAMLLIB%\libcamlidl.lib z3.cmxa test_mlapi.ml </code></pre> <p>I got the following error on executing <em>build.cmd</em> in the <em>Visual Studio 2008 Command Prompt</em></p> <pre><code>** Fatal error: Cannot find file "/nologo" File "caml_startup", line 1, characters 0-1: Error: Error during linking </code></pre> <p>On removing the <code>-ccopt "%XCFLAGS%"</code>, it works fine. The generated <em>exe</em> also executes as expected. ( Note that I have flexdll in PATH ). Any idea why this might be happening?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload