You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For users that use directly the robotology-superbuild, the fact that the robotology-superbuild install all its packages in <build>/install is typically the desired behaviour and clear. However, for some specific use case (for example installation in a Docker images) it is sometimes desirable to install all the package somewhere else, using the YCM_EP_INSTALL_DIR . At the moment, this variable is document in YCM documentation, but there is too hidden to be found easily by robotology-superbuild users. We should document this workflow, clarifying anyhow that this is only supported for one-shot installation of the superbuild, and not for usual use.
For users that use directly the robotology-superbuild, the fact that the robotology-superbuild install all its packages in
<build>/install
is typically the desired behaviour and clear. However, for some specific use case (for example installation in a Docker images) it is sometimes desirable to install all the package somewhere else, using theYCM_EP_INSTALL_DIR
. At the moment, this variable is document in YCM documentation, but there is too hidden to be found easily by robotology-superbuild users. We should document this workflow, clarifying anyhow that this is only supported for one-shot installation of the superbuild, and not for usual use.Related issues:
The text was updated successfully, but these errors were encountered: