summaryrefslogtreecommitdiff
path: root/src/basic/build.c
Commit message (Collapse)AuthorAgeFilesLines
* various: boldify version outputZbigniew Jędrzejewski-Szmek2023-02-091-1/+2
| | | | | | Follow-up for 4453ebe4db0511d25bed1040930ea6430c1bed91. With the feature list all dandified, the most important part of the output, i.e. the project name and version, are less visible.
* build: add some coloring to --version outputLennart Poettering2023-01-231-1/+45
| | | | Make it easier to discern enabled and disabled build options.
* meson: add version.h as dependency to more targetsZbigniew Jędrzejewski-Szmek2022-11-081-0/+1
| | | | | | | | | | | version.h can be generated after compilation starts, creating a race condition between compilation of various .c files and creation of version.h. Let's add it as a dependency to more build targets that require version.h or build.h. So far we played whack'a'mole by adding versiondep whenever compilation failed. In principle any target which includes compilation (i.e. any that has .c sources directly), could require this. I don't understand why we didn't see more failures… But it seems reasonable to just add the dependency more widely.
* basic: move version() to build.h+cZbigniew Jędrzejewski-Szmek2022-11-081-0/+9
|
* build: include status of TPM2 in the feature string show by --versionFranck Bui2022-03-291-0/+6
|
* build: include BPF_FRAMEWORK tag in version stringYu Watanabe2021-12-101-0/+6
|
* port string_hashsum from libgcrypt to openssl^gcryptZbigniew Jędrzejewski-Szmek2021-12-011-1/+1
| | | | | | | | This allows resolved and importd to be built without libgcrypt. Note that we now say either 'cryptographic library' or 'cryptolib'. Co-authored-by: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
* shared/build: make the version string definition less terribleZbigniew Jędrzejewski-Szmek2020-12-031-0/+216
The BLKID and ELFUTILS strings were present twice. Let's reaarange things so that each times requires definition in exactly one place. Also let's sort things a bit: the "heavy hitters" like PAM/MAC first, then crypto libs, then other libs, alphabetically, compressors, and external compat integrations. I think it's useful for users to group similar concepts together to some extent. For example, when checking what compression is available, it helps a lot to have them listed together. FDISK is renamed to LIBFDISK to make it clear that this is about he library and the executable.