Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

setting POWER_UTIL is not reflected in build #2

Closed
amagura opened this issue May 24, 2014 · 1 comment
Closed

setting POWER_UTIL is not reflected in build #2

amagura opened this issue May 24, 2014 · 1 comment
Labels
bug enhancement

Comments

@amagura
Copy link
Owner

amagura commented May 24, 2014

Description

Because there's no way to guarantee that (for whatever reason) vanilla acpi or pmset or whatever util ./configure has found and has chosen to use for the -DZELDA_BATTERY_UTIL=\"<UTIL>\" CPP flag, peeps should be able to explicitly specify a program/utility that should be used instead of whatever was chosen by ./configure. However, setting POWER_UTIL in the environment of the build does nothing. It should change the value of the ZELDA_BATTERY_UTIL CPP flag, but it doesn't.
@amagura amagura closed this as completed Dec 31, 2014
@amagura
Copy link
Owner Author

amagura commented Dec 31, 2014

Closed due to no longer being relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amagura