Changeset 8675:845fe8b83328 in orange


Ignore:
Timestamp:
08/12/11 14:51:45 (3 years ago)
Author:
Noughmad <Noughmad@…>
Branch:
default
Convert:
355896444faa554393aafd6e0fe3f2ad092d904b
Message:

Update the README file

File:
1 edited

Legend:

Unmodified
Added
Removed
  • source/orangeqt/README.txt

    r8669 r8675  
    1 == How to build the orangeplot library and its python bindings: == 
     1== How to build the orangeqt library: == 
    22 
    33= Prerequisites = 
    44 
    5 orangeplot uses CMake and SIP. They are both free software and are included in most Linux distributions.  
     5orangeqt uses CMake and SIP. They are both free software and are included in most Linux distributions.  
    66They can also be downloaded from their sites:  
    77 
     
    99SIP: http://www.riverbankcomputing.co.uk/software/sip/download 
    1010 
    11 orangeplot also needs the Qt libraries and headers (the qt-dev or qt-devel packages on Linux) and PyQt.  
     11orangeqt also needs the Qt libraries and headers (the qt-dev or qt-devel packages on Linux) and PyQt.  
     12 
     13The Qt libraries can be downloaded from Nokia: https://qt.nokia.com/downloads/downloads#qt-lib.  
     14 
     15Download and install the latest version of the libraries that matches your operating system and compiler. Different version of compilers are compatible, but different compilers are not.  
     16 
    1217 
    1318= Compilation = 
    1419 
    15 If you use GNU Make, it's enough to just call 'make' from the orangeplot directory 
     20If you use GNU Make, it's enough to just call 'make' from the orangeqt directory.  
    1621 
    17 Follow the standard CMake instructions to compile orangeplot: 
    18  1.a) Use the CMake GUI, and load the orangeplot directory from there.  
     22On windows, follow the standard CMake instructions to compile orangeqt: 
     23 1.a) Use the CMake GUI, and load the orangeqt directory from there.  
    1924    The build directory must be a new or empty directory, and is usually called build and placed inside the source directory. 
    2025    This method is preferred as it asks you for your compiler settings. 
     26 
    2127 1.b) From the command line: run  
    2228        mkdir build 
    2329        cd build 
    24         cmake -G "MinGW Makefiles" .. 
    25     If you use a compiler other than MinGW, replace "MinGW Makefiles" with the appropriate value.  
    26  2) Compile the program by calling 'make' in the build directory.  
    27  There is no need to call "make install", because "make" will copy both the C++ library and its Python bindings into the parent directory, with other Orange libraries.  
     30        cmake -G "NMake Makefiles" .. 
     31    If you use a compiler other than NMake, replace "NMake Makefiles" with the appropriate value.  
     32        The list of possible choices includes "Visual Studio 10", "Unix Makefiles", "NMake Makefiles" and many others.  
     33        It is exparing with every new compiler supported by CMake, the complete list is available in the GUI version of CMake.  
     34 
     35 2) This step depends on your selected compiler. If you chose any type of makefiles, run "make" or "nmake" in the build directory. If you used Visual Studio, open the Solution file located in the build directory.  
     36 
     37 There is no need to install the library, because CMake will copy both the library into the parent directory, with other Orange libraries. However, make sure that the generated library (orangeqt.so or orangeqt.pyd) is in Python's path. You can either adjust the path, or copy the library somewhere where Python will find it.  
    2838  
    29  Again, if you're using a different compiler or make, you may have to use 'nmake' instead of make, or compile the solution from within VisualStudio.  
    30  
    31 If any step reports an error, it is mostly likely some of the dependencies listed above are not installed or not found.  
     39 If any step reports an error, it is mostly likely some of the dependencies listed above are not installed or not found.  
Note: See TracChangeset for help on using the changeset viewer.