#199: Stop using recursive Makefiles in milena/tests/? ----------------------+----------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: proposal | Status: new Priority: trivial | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- 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.
#199: Stop using recursive Makefiles in milena/tests/? -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: minor | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Changes (by levill_r):
* priority: trivial => minor * version: 1.0 => 2.0 * type: proposal => task
Comment:
Quoting Akim in `tiger-patches` (« package: migrate the whole src tree to a single Makefile. »):
For the record, amongst the various tricks that were used in src/:
{{{ for i in **/local.mk do dir=$(dirname $i) case $dir in (ast|parse|task) continue;; esac perl -0777 -pi \ -e 's{\b(test_\w+)}{'"$dir"'_$1}g;' \ -e 's{(test-\w+)}{'"$dir"'/$1}g;' \ -e 's{\b([-\w.]+.\w+)\b}{'"$dir/"'$1}g;' \ -e 's{(\w+_SOURCES)}{'"$dir"'_$1}g;' $i done }}}
and tons of adjustments by hand.
I leaving [milestone:"Olena 2.1" Olena 2.1] as target, but we may want to postpone this task to [milestone:"Olena 2.2" Olena 2.2].
#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.
-
Olena Trac