pgrondek/polybar-dwm
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
dd03bb3c40
polybar-dwm/cmake/05-summary.cmake

61 lines
2.7 KiB
CMake
Raw Normal View History

refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
#
# Output build summary
#
message(STATUS " Build:")
refactor(cmake): Add version information to summary
2018-12-14 09:02:20 +00:00
message_colored(STATUS " Version: ${APP_VERSION}" "32;1")
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
message_colored(STATUS " Type: ${CMAKE_BUILD_TYPE}" "37;2")
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
if (HAS_CXX_COMPILATION)
cmake: Stop using CMAKE_* variables for flags It is not recommended anyway and the -Werror flag set in CI was getting set when compiling gtest, breaking our build.
2021-07-11 12:11:58 +00:00
message_colored(STATUS " CXX: ${CMAKE_CXX_COMPILER} ${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_${CMAKE_BUILD_TYPE_UPPER}} ${cxx_flags_str}" "37;2")
message_colored(STATUS " LD: ${CMAKE_LINKER} ${CMAKE_EXE_LINKER_FLAGS} ${CMAKE_EXE_LINKER_FLAGS_${CMAKE_BUILD_TYPE_UPPER}} ${cxx_linker_flags_str}" "37;2")
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
endif()
if (BUILD_DOC)
message_colored(STATUS " sphinx-build: ${BIN_SPHINX} ${SPHINX_FLAGS}" "37;2")
endif()
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
cmake: Use GNUInstallDirs (#1818) * Use GNUInstallDirs instead of hardcoded paths This change should be a no-op in the normal case and at the same time make it easier to customise polybar builds on systems with special needs. * Avoid creating /usr/share/doc/polybar/polybar/* * Include GNUInstallDirs for the doc target itself * cmake: Don't try to set CMAKE_INSTALL_* variables Since we include GNUInstallDirs all these variables are already set * cmake: Print install directories in summary * fix(cmake): Make doc-only work like normal build This is kind of a dirty hack to force CMAKE_INSTALL_DOCDIR to use `polybar` as the project name when only polybar-doc is built. Maybe it is wiser at some point to be able to do a doc only build (and install) that can be done from the top level project. Then we would also not need to include GNUInstallDirs here
2019-06-24 16:08:59 +00:00
message(STATUS " Install Paths:")
message_colored(STATUS " PREFIX: ${CMAKE_INSTALL_PREFIX}" "32")
message_colored(STATUS " BINDIR: ${CMAKE_INSTALL_FULL_BINDIR}" "32")
message_colored(STATUS " DATADIR: ${CMAKE_INSTALL_FULL_DATADIR}" "32")
message_colored(STATUS " DOCDIR: ${CMAKE_INSTALL_FULL_DOCDIR}" "32")
message_colored(STATUS " MANDIR: ${CMAKE_INSTALL_FULL_MANDIR}" "32")
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
message(STATUS " Targets:")
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
colored_option(" polybar" BUILD_POLYBAR)
colored_option(" polybar-msg" BUILD_POLYBAR_MSG)
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
colored_option(" testsuite" BUILD_TESTS)
refactor(cmake): Make documentation optional
2018-12-14 09:12:42 +00:00
colored_option(" documentation" BUILD_DOC)
build: Add option to enable/disable html/manpages
2020-12-22 11:29:26 +00:00
colored_option(" html" BUILD_DOC_HTML)
colored_option(" man" BUILD_DOC_MAN)
Documentation update for 3.6
2022-03-02 13:36:54 +00:00
colored_option(" default config" BUILD_CONFIG)
cmake: Add option to enable/disable shell files
2020-12-24 00:09:39 +00:00
colored_option(" shell files" BUILD_SHELL)
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
if (BUILD_LIBPOLY)
message(STATUS " Module support:")
colored_option(" alsa" ENABLE_ALSA ALSA_VERSION)
colored_option(" curl" ENABLE_CURL CURL_VERSION)
Merge tag '3.6.3' Search for xcbgen with PYTHON_EXECUTABLE This way users can specify `-D:PYTHON_EXECUTABLE` to force a certain python executable and that executable will then also be used to search for xcbgen. This should also provide a more universal solution to the configuration issues with pyenv or conda since the user can just specify `-D:PYTHON_EXECUTABLE=/usr/bin/python3`.
2023-08-05 16:42:20 +00:00
colored_option(" dwm" ENABLE_DWM)
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
colored_option(" i3" ENABLE_I3)
colored_option(" mpd" ENABLE_MPD MPD_VERSION)
colored_option(" network (${WIRELESS_LIB})" ENABLE_NETWORK NETWORK_LIBRARY_VERSION)
colored_option(" pulseaudio" ENABLE_PULSEAUDIO PULSEAUDIO_VERSION)
colored_option(" xkeyboard" WITH_XKB Xcb_XKB_VERSION)
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
message(STATUS " X extensions:")
colored_option(" xcb-randr" Xcb_RANDR_FOUND Xcb_RANDR_VERSION)
colored_option(" xcb-randr (monitor support)" WITH_XRANDR_MONITORS Xcb_RANDR_VERSION)
colored_option(" xcb-composite" Xcb_COMPOSITE_FOUND Xcb_COMPOSITE_VERSION)
colored_option(" xcb-xkb" WITH_XKB Xcb_XKB_VERSION)
colored_option(" xcb-xrm" WITH_XRM Xcb_XRM_VERSION)
colored_option(" xcb-cursor" WITH_XCURSOR Xcb_CURSOR_VERSION)
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
message(STATUS " Log options:")
colored_option(" Trace logging" DEBUG_LOGGER)
logger: Enable trace logging by default Often we may need information from the user that is only available if -l trace is used which requires most users to recompile polybar in debug mode.
2018-02-26 20:09:51 +00:00
refactor(cmake): Allow targets to be enabled individually Each major target of polybar can now be enabled/disabled while configuring (even polybar itself). The cmake code specific to each target will only run if the target is enabled. This allows us to for example just build the documentation without having to run all the cmake code related to compilation or having the polybar dependencies installed (other than sphinx).
2020-12-22 02:43:06 +00:00
if(CMAKE_BUILD_TYPE_UPPER MATCHES DEBUG)
message(STATUS " Debug options:")
colored_option(" Trace logging (verbose)" DEBUG_LOGGER_VERBOSE)
colored_option(" Draw clickable areas" DEBUG_HINTS)
colored_option(" Print fc-match details" DEBUG_FONTCONFIG)
endif()
refactor(cmake): Cleanup
2017-01-26 16:17:02 +00:00
endif()
Reference in New Issue Copy Permalink