FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

LinkBack Thread Tools
Old 10-13-2012, 11:43 AM
Michał Górny
Default Common build directory variable (for cmake-utils & autotools-utils)


The new python-r1 eclass provides a python_foreach_impl() function
which runs given command for each python implementation, in its
respective build directory.

This function collides a bit with the build-dir functionality provided
in cmake-utils and autotools-utils. If used to spawn the phase
functions of those eclasses, it first enters the correct (python
implementation-specific) build directory, then the eclass re-enters its
own, chosen build directory.

In order to work-around that, users either have to:

a) wrap all phase functions in custom wrapper which set CMAKE_BUILD_DIR

b) use cheap tricks like setting CMAKE_BUILD_DIR=. globally (untested).

Both solutions being not really that good, I think it would be useful
to use a common BUILD_DIR variable for all eclasses. In that case,
python-r1 would just set BUILD_DIR, and cmake-utils or autotools-utils
phase functions would just use that instead of FOO_BUILD_DIR.

What are your thoughts?

Best regards,
Michał Górny

Thread Tools

All times are GMT. The time now is 07:44 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org