Project

General

Profile

Logged in as brainvisa

Distribution policy

Currently, we distribute a global BrainVISA package that contains various software:
- Anatomist, the visualization software
- Axon, the core Brainvisa software
- Several Brainvisa toolboxes: Brainrat, Connectomist, Cortical surface, Freesurfer, Nulcear imaging, Sulci, T1 MRI, ...
- Aims, the image processing library and commands
- Soma-workflow, the parallel computing software
...

Sooner or later, we should distribute these software as several independant packages according to their licenses. This would allow to have a customized installation of Brainvisa with a set of toolboxes chosen by the user. But we would like to develop a practical installer program before dividing the distribution into several packages to ease the installation.

How to add something to the current distribution ?

Developing in existing projects

One easy way of adding your contribution to the current distribution is to develop in one of the existing projects of the repository that are included in the Brainvisa packages.
A modification done in the last bug_fix (branches/x.y) branch of a project will be included in the next patch release of Brainvisa (version x.y.z).
A modification done in the trunk branch of a project will be included in the next minor or major release of Brainvisa (version x.y.0).

See this page about the organisation of the repository for more information.

Adding a new project

If you want to create a new project in the repository to host your developments, it is also possible to add it to the distribution of Brainvisa. To do so, please contact one of the managers of the Brainvisa project to discuss it (https://bioproj.extra.cea.fr/redmine/projects/brainvisa).

How to distribute an additional package for Brainvisa ?

Alternatively, you can distribute your toolbox as an additional package for Brainvisa that would be downloaded and installed in addition of Brainvisa main package.

It can be useful for various reasons:
- To be able to distribute new versions of the tool more often than Brainvisa main package releases
- To have a better visibiliy of the tool and its authors
- To distribute the tool on another website
- To use another repository for the sources
...

Even if you distribute your tool as an additional package, it is still possible to use the packaging tools available in development/brainvisa-cmake component.
See this page about how to use bv_packaging script and this page about how to write CMakeLists files to build a project with brainvisa-cmake.

Also available in: PDF HTML TXT