#199: Stop using recursive Makefiles tests
-----------------------+------------------------
Reporter: levill_r | Owner: Olena Team
Type: task | Status: new
Priority: minor | Milestone: Olena 2.1
Component: Milena | Version: 2.0
Resolution: | Keywords:
-----------------------+------------------------
Old description:
This is an open debate, not a well-defined task.
As of r3946, there are more than a hundred `Makefile`s under
source:trunk/milena/tests/. This has a huge impact on configuration and
build times.
Akim suggests we use `Makefile` inclusions instead of `Makefile`
recursion to speed up things. This also means losing the possibility to
invoke `make` in a specific subdirectory of `milena/tests/`, which is
very handy. Akim says we can substitute the feature by using scripts
relying on the control version program (
http://lists.gnu.org/archive/html
/automake-patches/2009-03/msg00079.html).
Let's discuss this, and see what we can do after the 1.0 release.
New description:
As of September 6, 2013, there are more than a hundred `Makefile`s under
source:milena/tests/. This has a huge impact on configuration and build
times.
Akim suggests we use `Makefile` inclusions instead of `Makefile` recursion
to speed things up, as he did in TC. This also means losing the
possibility to invoke `make` in a specific subdirectory of
`milena/tests/`, which is very handy. Akim says we can substitute the
feature by using scripts relying on Git (see
http://lists.gnu.org/archive/html/automake-patches/2009-03/msg00079.html).
We also probably want to apply this to transformation to Scribo, which
contains 17 Makefiles under source:scribo/tests/.
--
Comment (by levill_r):
Update the description and mention the case of Scribo.
--
Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/199#comment:2>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient image processing platform