1 |
Currently, each of the mentioned eclasses has its own *_BUILD_DIR. |
2 |
Therefore, if someone needs to provide a custom BUILD_DIR, he needs to |
3 |
set it explicitly for the eclass. This is fine for ebuilds but not |
4 |
really neat for eclasses. |
5 |
|
6 |
The idea is simple: use a common BUILD_DIR instead. For compatibility, |
7 |
export AUTOTOOLS_ & CMAKE_BUILD_DIR as well but prefer the former one. |
8 |
For most of the ebuilds this won't make a difference. |
9 |
|
10 |
I'm attaching an example conversion of pygobject where this would |
11 |
benefit. The idea is quite simple; ebuild calls |
12 |
|
13 |
python_foreach_impl autotools-utils_src_... |
14 |
|
15 |
python_foreach_impl() sets BUILD_DIR for each implementation, |
16 |
autotools-utils phases use that and everything simply works! |