GitLab

We don't want to re-generate the recombinations each time we launch the
process. It would certainly be convenient to have the recombinations
generated when the files do not exist. But I didn't succeed to specify a
joker in the dependance list.

Random recombinations with random deletions and insertions at the
junction and mismatches in the sequence (1%)

Since 43d2a3fe, errors in make_tools were ignored.
The syntax is now ugly, but it works.

We should not launch a command directly but use variables instead.
The standard variable for make is $(MAKE). It is therefore more portable
(for instance on freebsd where the make command used should be gmake)

We must clean the repertory first since Vidjil had previously be compiled for
tests (-O0 -g) and we don't want a release executable with such options.

The name of the executable depends on the architecture and on the release name.

It fails when the python version is incorrect.

cleancoverage removes coverage-related files
cleantests removes test-related files
cleanall removes everything.

We want to be able to test coverage on different rules, without
deleting previous coverage files.

Gather should and shouldvdj rules. Used for coverage.

.should-vdj.fa tests (algo)
.should_get tests (tools)
data/*.vidjil, data/*.analysis

shouldvdj_generated_kmer -> a few seconds (-2q)
shouldvdj_generated_fine -> a few minutes

The 'test_with_fuse' rule was not used. As we now ship fuse.py with the algo release,
fuse.py doctests can be always checked, and the right place to do that is tools/tests/Makefile.

At the end of the release, we test 'make unit_browser', but this rule
does currently not fail when there is a problem.