Go to file
Daniel Eklöf a385b761bd Append to CFLAGS, instead of replacing them
The makefile already use (directly, or indirectly) CPPFLAGS and
LDFLAGS, so it makes sense to also use the user provided CFLAGS.

One example where this is necessary is if the user has set
CPPFLAGS=”-D_FORTIFY_SOURCE=2”, which, before this patch, results
in (even if the user has set CFLAGS=-O2):

/usr/include/features.h:397:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) -Werror=cpp]
2021-08-06 23:30:59 +02:00
.builds Add sourcehut build job 2021-08-05 22:07:53 +02:00
.gitignore Implement everything 2021-06-14 21:35:52 +00:00
LICENSE init 2021-06-14 21:35:38 +00:00
Makefile Append to CFLAGS, instead of replacing them 2021-08-06 23:30:59 +02:00
README init 2021-06-14 21:35:38 +00:00
wlopm.1 Merge branch 'manpage' 2021-07-17 15:41:59 +02:00
wlopm.c Make compiler flags more aggressive 2021-06-29 15:51:02 +02:00
wlr-output-power-management-unstable-v1.xml Implement everything 2021-06-14 21:35:52 +00:00
xdg-output-unstable-v1.xml Implement everything 2021-06-14 21:35:52 +00:00

wlopm - Wayland output power management

Simple client implementing zwlr-output-power-management-v1.