Tuning the build process – pre 0.16.0

Before openvibe 0.16.0 the build process was tuned inside the win32-init_env_command or linux-init_env_command. Since then the build has changed and the tuning process is described in the Building OpenViBE/Tuning the build process page.

If you wish to use an older openvibe then you should follow these instructions:

If you want to customize the build process, modify the init_env_command script. In case you have trouble using your modified script, the skeletons may represent useful backups. Here are some tips for common developer needs :

  • Default behaviour: The script will build all the modules, except the documentation (that you find on the website anyway). After a fresh checkout, please build the software like this once.
  • Build a branch instead of module’s trunk: Modify the init_env_command script by specifying the branch path. For example, if you want to try a specific – unstable – driver located in a branch on Windows:
    SET OpenViBE_application_acquisition_server_branch=

    will become :

    SET OpenViBE_application_acquisition_server_branch=branches/wip-unstable-driver

    if you want to try a specific – unstable – driver located in a branch on Linux:

    OpenViBE_application_acquisition_server_branch=

    will become :

    OpenViBE_application_acquisition_server_branch=branches/wip-unstable-driver
  • Build only few modules (will work only if all modules have been compiled at least once): Modify the init_env_command script by choosing the project to be added in the build order. For example if you want to rebuild the signal processing plugin on Windows:
    echo %OpenViBE_plugin_signal_processing% >> %OpenViBE_build_order%

    If you want to avoid building the signal processing plugin on Windows, just remove the line or comment it like this:

    REM echo %OpenViBE_plugin_signal_processing% >> %OpenViBE_build_order%

    Similarly, if you want to rebuild the signal processing plugin on Linux:

    $OpenViBE_plugin_signal_processing

    If you want to avoid building the signal processing plugin on Linux, just remove the line or comment it like this:

    #$OpenViBE_plugin_signal_processing
This entry was posted in Deprecated and old documents. Bookmark the permalink.