Bug 217638 - set-env in the global section not being set per module?
Summary: set-env in the global section not being set per module?
Status: RESOLVED FIXED
Alias: None
Product: kdesrc-build
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-06 21:30 UTC by Raphael Kubo da Costa
Modified: 2010-01-10 06:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Raphael Kubo da Costa 2009-12-06 21:30:49 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

When using "set-env" in the global section, the variable isn't set when a module is built.

By using -p and --debug, the debug output shows "Would have set ..." before "Options for module global", but it isn't shown inside "Building <module>". Besides, the enviroment variable isn't set when a module is built.
Comment 1 Michael Pyne 2010-01-10 06:31:17 UTC 
SVN commit 1072397 by mpyne:

Ensure that global set-env's are performed for each module in addition to the module's own
defines. (This was broken after the switch to resetting env vars for each module).

BUG:217638


 M  +5 -2      kdesvn-build  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1072397