Age | Commit message (Collapse) | Author |
|
... by renaming test/end-to-end/targets.
(cherry-picked from d95d8121199e2519aa441cb1a471cf5aec69574d)
|
|
... as well as the already present -Wno-error. In this way,
packagebuilding should work out of the box on more systems.
(cherry-picked from 5abcd4140a91236c7bda1c21ce69e76a28da7c8a)
|
|
(cherry-picked from 82e0bd818aee1ca8751e0abf20455af88cc513bf)
|
|
|
|
|
|
(cherry picked from 53ba5581070bc8914a35a5e16af901c562923e61)
|
|
(cherry picked from 3e4e2b6fcbffe5de62d7c3eab47fdf3987dc778d)
|
|
... std::hash<fs::path> was first implemented in libstdc++
version 12. However, that change was also backported to
bug-fix release 11.4, so we may not include our
reimplementation if that version is used.
(cherry picked from 8fb4a41a63e5d195c2463ce0bc75e9d41cc0c5be)
|
|
The formatter is based on fmt's ostream_formatter, using the provided
operator<<(std::ostream&) of nlohmann::basic_json. This is required to
allow compilation against fmt 10.x
(cherry picked from 601d546b8452159c38d65231d52f0dbd05e793d2)
Co-authored-by: Oliver Reiche <oliver.reiche@huawei.com>
|
|
... to improve portability
(cherry picked from 2b2719c7507437d722ad673d8c563f1c54974770)
|
|
|
|
|
|
|
|
... causing an error with gcc 13.2.0.
|
|
|
|
|
|
... to silence false-positive 'possible dangling reference'
warning produced by gcc 13.2.0.
|
|
... on next invocation, instead of being taken from cache.
|
|
... which are only actions that, besides giving exit code 0 also
created all the outputs they promised to.
|
|
... to suppress 'unused function' warnings.
|
|
|
|
... by moving the diagnose and cli related code into to separate
libraries. In this way, we hopefully improve maintainability of
the code base.
|
|
...by moving subcommands code into separate libraries.
This maintains a cleaner code structure and lowers the build time
by improving target caching.
|
|
|
|
|
|
|
|
Old K&R function definitions got cleaned upstream, which removes
many warnings when building zlib with more recent compilers.
|
|
... by disabling auto-configuration. The problem that the result
of this auto-configuration depends on the language standard used
and may (and in case of libproto does) leak into public interfaces
of consuming libraries; this would require every user of a library
with a public dependency of absl to use the same language standard
that library was built with. Such a requirement makes the rules
hard to use in a portable way.
|
|
|
|
... and use "linux" as default for OS. If TARGET_ARCH is
"arm" or not set, link against -latomic (for required
targets).
|
|
|
|
While there,
- remove the outdated claim that in package build of just the prebuilt
library aproach of a header-only library with link dependencies
is chosen, and
- remove a wrong footnote separator.
|
|
... while providing a native descirption still is the cleaner approach.
Nevertheless, hinting on this fact early avoids scaring off novice
users having a lot of dependencies.
|
|
... and document at the appropriate place
|
|
... and mention it at the appropriate part of the documentation.
While there, also provide a default TARGETS file.
|
|
... and document at the appropriate places what can be overwritten
by setting those targets.
|
|
... as a way to find out more about the defining rule of a target.
While there, also be a bit more explicit about target naming and the
fact that the default target is a target of the rules repository.
|
|
... emphasizing that source files are just targets and that we
could as well use a defined target there.
|
|
|
|
|
|
... to pass along toolchain settings for current and future
toolchain definitions. Configuration variable
COMPILER_FAMILY is replaced by TOOLCHAIN_CONFIG["FAMILY"].
|
|
|
|
|
|
... and extend compatibility by not relying on arguments
that are only supported by GNU patch implementations.
|
|
... because it was using tool that are not part of
coreutils. Using patch parts can still be done via patching
patches.
|
|
... instead of creating an ENV from it and propagating this.
The idea is to keep PATH entries separate and only join them
with ":" when we need it. In this way, we can accumulate
PATHs from multiple defaults later, and perform a
deduplication ("nub_left") to shorten the final string
length.
|
|
|
|
|
|
|
|
|