You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

INSTALL.md 3.2KB

2 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. Dependencies
  2. ============
  3. Linux Ubuntu (14.04 and 16.04)
  4. -----------------------------
  5. - Install the dependencies
  6. - run `linux-install-dependencies.pl` script; you will require sudo rights
  7. - run `unix-get-dependencies.sh` script with an existing `DEPENDENCY_CACHE` environment variable or with --cache parameter (OPTIONAL - for tests),
  8. or with `PROXYPASS`
  9. Windows 7 and later
  10. -------------------
  11. - Install the dependencies:
  12. - copy `windows-install-dependencies.cmd` and rename copy to `windows-install-dependencies-custom.cmd`
  13. - edit line `set PROXYPASS=XXX:XXX` with appropriate username and password
  14. - run it whenever you want to update dependencies.
  15. Install
  16. =======
  17. Linux Ubuntu (14.04)
  18. --------------------
  19. - Build the sofware
  20. - run `unix-build` script, and append `--build-unit` and/or `--build-validation` if you want to build tests
  21. - Run unit tests
  22. - run `ctest-launcher.sh` from the build directory
  23. Windows 7 and later
  24. -------------------
  25. - Build the sofware
  26. - run `windows-build.cmd` script, and append `--build-unit` and/or `--build-validation` if you want to build tests
  27. - Run unit tests
  28. - run `ctest-launcher.cmd` from the build directory
  29. Building Documentation
  30. ======================
  31. Documentation Dependencies
  32. --------------------------
  33. The documentation is build by the sphinx tool and has following dependencies:
  34. * Python
  35. * sphinx
  36. * sphinx_rtd_theme
  37. The best way to have these dependencies ready is to use a virtualenv in order to make an environment containing these.
  38. Assuming you have virtualenv installed the commands would be:
  39. First time:
  40. mkdir -p ~/virtualenvs
  41. virutalenv ~/virtualenvs/openvibe-doc
  42. source ~/virtualenvs/openvibe-doc/bin/activate
  43. pip install sphinx sphinx_rtd_theme
  44. or on windows
  45. md %USERPROFILE%\virtualenvs
  46. virtualenv %USERPROFILE%\virtualenvs\openvibe-doc
  47. %USERPROFILE%\virtualenvs\openvibe-doc\Scripts\activate.bat
  48. pip install sphinx sphinx_rtd_theme
  49. once the environment is created you only need to execute the third line to activate it.
  50. Documentation Building
  51. ----------------------
  52. The documentation main files reside in documentation/sphinx folder and is constructed in the following fashion:
  53. 1. During the CMake step documentation files are pooled in the dist/doc-tmp/sphinx folder
  54. * The files come from the documentation/sphinx folder and from the plugins `boxes` folders
  55. 2. The documentation will generate a build-documentation script inside the doc-tmp folder which
  56. has to be launched manually.
  57. 3. The documentation will be generated in the `doc-tmp/sphinx/build` folder and moved to
  58. `doc/OpenViBE Manual`
  59. Extending Documentation
  60. -----------------------
  61. If you wish to build a documentation that extends what is already in the SDK you can do so by adding files
  62. into the doc-tmp folder and overwriting indexes.
  63. A few remarks:
  64. The main index file is in `doc-tmp/sphinx/source/index.rst` and should almost always be overwritten if you
  65. need to add something to the documentation.
  66. Box list is in `doc-tmp/sphinx/source/boxes/index-boxes.rst`. The plugin-inspector can generate this file
  67. for you using the `openvibe-plugin-inspector --box-doc-directory <WHERE>` template. It will also generate
  68. templates for all boxes that can be loaded by the kernel.