Using Microsoft Visual C++

1. XSB will unpack into a subdirectory named xsb. Assuming that you have XSB.ZIP in the $XSB_DIR directory, you can issue the command

   
      unzip386 xsb.zip
   

   which will install XSB in the subdirectory xsb.

2. If you decide to move XSB to some other place, make sure that the entire directory tree is moved -- XSB executable looks for the files it needs relatively to its current position in the file system.

You can compile XSB under Microsoft Visual C++ compiler to create a console-supported top loop or a DLL by following these steps:

1. cd build

2. Type:
   makexsb_wind "CFG=option" ["DLL=yes"] ["ORACLE=yes"] ["SITE_LIBS=libraries"]
   • The items in square brackets are optional.
   • The options for CFG are: release or debug. The latter is used when you want to compile XSB with debugging enabled.
   • The other parameters to makexsb_wind are optional. The DLL parameter tells Visual C++ to compile XSB as a DLL. The ORACLE parameter compiles XSB with support for Oracle DBMS. If ORACLE is specified, you must also specify the necessary Oracle libraries using the parameter SITE_LIBS.

3. The above command will compile XSB as requested and will put the XSB executable in:
   
   $$\tt \$XSB\_DIR\backslash config\backslash \mbox{\tt x86-pc-windows}\backslash bin \backslash xsb.exe$$
   
   
   If you requested to compile XSB as a DLL, then the DLL will be placed in
   
   $$\tt \$XSB\_DIR\backslash config\backslash \mbox{\tt x86-pc-windows}\backslash bin \backslash xsb.dll$$
   
   

Note: the XSB executable and the DLL can coexist in the same source tree structure. However, if you first compiled XSB as an executable and then want to compile it as a DLL (or vice versa), then you must run

 makexsb_wind  clean

in between.