Commit 6af3d44c authored by Jaden's avatar Jaden Committed by Flavio TARSETTI

update docs for correct bdt usage & templates section

parent 2ffc2bcd
[buildout]
parts = scripts
parts = scripts templates
eggs = beat.editor
develop = .
newest = false
[scripts]
recipe = bob.buildout:scripts
[templates]
recipe = collective.recipe.cmd
cmds = ./bin/python conda/linkeditor.py
on_install = true
on_update = true
......@@ -26,20 +26,15 @@ Installation Steps
$ git clone git@gitlab.idiap.ch:beat/beat.editor.git
$ cd beat.editor
#. Build a development Conda environment using `the Bob/BEAT CLI tool <https://www.idiap.ch/software/bob/docs/bob/bob.devtools/master/install.html>`_: ::
#. Create a generic development Conda environment for the BEAT/Bob ecosystem using `the Bob/BEAT CLI tool <https://www.idiap.ch/software/bob/docs/bob/bob.devtools/master/install.html>`_: ::
$ conda create -n bdt -c https://www.idiap.ch/software/bob/conda bob.devtools
#. We will need the ``buildout`` command, so install the `bob.buildout` package to the new environment as well: ::
$ conda install -n bdt -c https://www.idiap.ch/software/bob/conda bob.buildout
#. Activate the created environment and use the ``bdt`` command from ``bob.devtools`` to build the ``beat.editor`` package: ::
#. Activate the created environment and use the ``bdt`` command from ``bob.devtools`` to create a Conda environment for the ``beat.editor`` package: ::
$ conda activate bdt
$ bdt build
$ bdt create beat_editor
#. For development, we want to generate all our CLI tools in the ``beat.editor`` project folder. Add the line ``dependent-scripts = true`` to ``buildout.cfg`` under the ``[scripts]`` section and use the ``buildout`` command to generate all the package's executables in ``bin/``: ::
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment