Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: Gentoo Developer Mailing List <gentoo-dev@l.g.o>
Subject: [gentoo-dev] [RFC] Common build directory variable (for cmake-utils & autotools-utils)
Date: Sat, 13 Oct 2012 11:43:53
Message-Id: 20121013134318.7122bf27@pomiocik.lan
1 Hello,
2
3 The new python-r1 eclass provides a python_foreach_impl() function
4 which runs given command for each python implementation, in its
5 respective build directory.
6
7 This function collides a bit with the build-dir functionality provided
8 in cmake-utils and autotools-utils. If used to spawn the phase
9 functions of those eclasses, it first enters the correct (python
10 implementation-specific) build directory, then the eclass re-enters its
11 own, chosen build directory.
12
13 In order to work-around that, users either have to:
14
15 a) wrap all phase functions in custom wrapper which set CMAKE_BUILD_DIR
16 or AUTOTOOLS_BUILD_DIR,
17
18 b) use cheap tricks like setting CMAKE_BUILD_DIR=. globally (untested).
19
20 Both solutions being not really that good, I think it would be useful
21 to use a common BUILD_DIR variable for all eclasses. In that case,
22 python-r1 would just set BUILD_DIR, and cmake-utils or autotools-utils
23 phase functions would just use that instead of FOO_BUILD_DIR.
24
25 What are your thoughts?
26
27 --
28 Best regards,
29 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature