Commits

Aleš Erjavec committed 50bf3f0

Updated the BUILDING instructions.

  • Participants
  • Parent commits cc98def

Comments (0)

Files changed (1)

-To compile Orange, you need Python 2.2 or later. You don't
+To compile Orange, you need Python 2.5 or later. You don't
 need Python sources, except for the header and library files
 that come with the basic distribution anyway.
 
 This file does not cover building the C4.5 plugin.
 See doc/reference/C45Learner.htm for instructions.
 
-You don't need C4.5 sources to build Orange on Linux and
-Mac OS X (as was the case with previous versions of Orange).
-
 Please report any problems to janez.demsar@fri.uni-lj.si.
 
 
-Compiling instructions for MSVC 6.0
+Compiling instructions for MSVC 2008
 -----------------------------------
 
-Although the provided project files are for MS VC 6.0, Orange
-can (in principle; we are not regularly checking it) also be
-compiled by MS VC .Net - just let it import and convert the files.
+The provided project files are for MS VC 2008.
 
 1.  Set the environment variable PYTHON to Python's root (e.g.
-    c:\python23). This is used for finding include files and libraries.
+    C:\Python27). This is used for finding include files and libraries.
 
-2.  The workspace file is in subdirectory source. Open it and
+2.  The VS Solution file is in subdirectory source. Open it and
     compile. Note that if you want to compile a debug version of
     Orange, you'll need to have the debug version of Python as
-    well (python23_d.lib, python23_d.dll etc). See file
+    well (python27_d.lib, python27_d.dll etc). See file
     debugging_orange.txt if you need a hint on that.
 
 3.  Make sure that Python will find the compiled modules. You can set
 Compiling instructions for Linux
 --------------------------------
 
-To compile orange, you'll need a newer gcc (version 3.2 works;
+To compile orange, you'll need a newer gcc (version 4.0 works;
 we are not sure about older compilers).
 
 1.  Run make (Makefile is in subdirectory source).
 4. Make sure with 'otool -L' that paths to dynamic libraries
    modules are using are correct. If not, use 'install_name_tool'
    to correct them.
+   
+   
+Linking with external libraries on Linux and Mac OSX
+----------------------------------------------------
+ 
+Pass the library names to make on the command line or through
+env. variables (you can also just edit the Makefile).
+Example:
+
+	make BLAS_LIB=atlas
+
+See the Makefile for more information.
+
+On Windows this is unsupported.