Changeset 983 for library/doc/tutorial/000install.dox
- Timestamp:
- 05/25/10 22:33:29 (14 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
library/doc/tutorial/000install.dox
r948 r983 6 6 7 7 BDM comes in two basic versions: 8 \li\b binary with precompiled executables and matlab mex files that can be configured by external text files9 \li\b source \b code that can be compiled into any required form.8 - \b binary with precompiled executables and matlab mex files that can be configured by external text files 9 - \b source \b code that can be compiled into any required form. 10 10 11 11 \section in_bin Binaries for BDMtoolbox … … 13 13 14 14 Installation: 15 \lisvn checkout http://mys.utia.cas.cz:1800/svn/mixpp/applications/bdmtoolbox/ into your local directory of your choice (this will be denoted \<toolbox_dir\>)16 \lior download a prepared zip file from http://staff.utia.cas.cz/smidl/Public/bdmtoolbox_win32.zip and extract it to any directory (will be denoted \<toolbox_dir\>)17 \liopen matlab and type:15 - svn checkout http://mys.utia.cas.cz:1800/svn/mixpp/applications/bdmtoolbox/ into your local directory of your choice (this will be denoted \<toolbox_dir\>) 16 - or download a prepared zip file from http://staff.utia.cas.cz/smidl/Public/bdmtoolbox_win32.zip and extract it to any directory (will be denoted \<toolbox_dir\>) 17 - open matlab and type: 18 18 \code 19 19 >> addpath <toolbox_dir>/mex; … … 29 29 \endcode 30 30 For linux, the default build dir is \<toolbox_dir\>/mex, hence only me and mex_classes need to be in the path. 31 \lithe toolbox is ready to be used, test it e.g. by:31 - the toolbox is ready to be used, test it e.g. by: 32 32 \code >> cd tutorial/userguide; 33 33 >> pdfds_example \endcode 34 \liif no error is given, the toolbox is installed correctly35 \liproceed to tutorial at http://mys.utia.cas.cz:1800/trac/bdm/doxygen/pages.html to learn how to use it34 - if no error is given, the toolbox is installed correctly 35 - proceed to tutorial at http://mys.utia.cas.cz:1800/trac/bdm/doxygen/pages.html to learn how to use it 36 36 37 37 \section src Source code … … 47 47 48 48 You need to have the following tools available on your system: 49 \liworking C++ compiler, e.g. gcc on Linux, or Visual Studio on windows50 \liCMake, a cross-platform build system, http://www.cmake.org49 - working C++ compiler, e.g. gcc on Linux, or Visual Studio on windows 50 - CMake, a cross-platform build system, http://www.cmake.org 51 51 52 52 \section lin Linux … … 89 89 Compilation of BDM: 90 90 91 *When everything is set-up, make a copy of library\system\win32\run_cmake.bat, edit it91 - When everything is set-up, make a copy of library\system\win32\run_cmake.bat, edit it 92 92 to reflect your environment (i.e. change paths to cmake and your C++ target environment) 93 93 and run it. 94 94 95 *Alternatively, you can run CMake GUI and specify address to your \<bdm_dir\>95 - Alternatively, you can run CMake GUI and specify address to your \<bdm_dir\> 96 96 97 97 98 *It should generate build files for your compiler in the main BDM98 - It should generate build files for your compiler in the main BDM 99 99 directory 100 100 … … 108 108 109 109 Right now, Cmake configuration is hard-coded for one testing machine. Look for the paths in SetBDMEnv.cmake and correct them. 110 Open CMake GUI, cli sk Configure followed by Create.110 Open CMake GUI, click Configure followed by Create. 111 111 Configuration files for your favourite build environment should be created in the BDM directory. 112 112