| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
This update also removes upb as external dependency.
Co-authored-by: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com>
|
|
...as required by grpc v1.53.0
|
|
Co-authored-by: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com>
|
|
|
|
|
|
... with two minor code base changes compared to previous
use of gsl-lite:
- dag.hpp: ActionNode::Ptr and ArtifactNode::Ptr are not
wrapped in gsl::not_null<> anymore, due to lack of support
for wrapping std::unique_ptr<>. More specifically, the
move constructor is missing, rendering it impossible to
use std::vector<>::emplace_back().
- utils/cpp/gsl.hpp: New header file added to implement the
macros ExpectsAudit() and EnsureAudit(), asserts running
only in debug builds, which were available in gsl-lite but
are missing in MS GSL.
|
|
|
|
... as the BUILD.bazel files that are the basis for the TARGETS
files seen to declare the dependencies in an incomplete way. Target
`grpc_base_c` needs `grpc_init()` and `grpc_shutdown()` from target
`grpc` (source `init.cc`). Adding this target dependency results
in a cycle.
This commit solves the issue by producing fewer but larger
libraries (as done in GRPC's CMakeLists.txt):
- `libgpr.a`: all gpr code
- `libgrpc.a`: all gprc code, depending on `libgpr.a`
- `libgrpc++.a`: all grpc++ code, depending on `libgrpc.a`
|
|
... now that we're using the unpatched version (after adding a
work around in our code base).
|
|
Major version release, with important fixes for our use-case.
|
|
This is the last (and recommended) revision of minor v1.5.
|
|
The distdir should only contain the direct dependencies of just.
Co-authored-by: Klaus Aehlig <klaus.aehlig@huawei.com>
|
|
|
|
tests have been updated accordingly
|
|
|
|
|
|
|
|
remote endpoint
|
|
Main updates to build description:
- remove unused defines of type "HAVE_<lib>_H"
- add new variables that allow users to set explicitly the presence of some lib symbols
- replace most defines of type "HAVE_<lib>" with "USE_<lib>" (to match the flag names)
- added GLOBs (where it made sense) for increased maintainability
|
|
Changes in build description:
- fix capitalization of ENABLE_LIBGCC flag.
- add new HIDE_SYMBOLS flag to allow hiding of export symbols; used
similar logic as for libcurl to circumvent the original
CHECK_C_SOURCE_COMPILES macro use.
|
|
Changes to build description:
- new USE_SHA256 flag
- removed "Generic" option for USE_SHA1
- updated to the new source code structure
(split "src/git2" into "src/libgit2" and "src/util")
|
|
... while following symbolic links. In this way, bootstrapping
is possible against preinstalled dependencies that symbolic links
or special files in their directories.
|
|
Co-authored-by: Michael Thies <mail@mhthies.de>
|
|
A lot of the dependencies in the "just" repository are not for
building just itself, but are used the the just-mr tool or for
testing. As the bootstrap process, however, only bootstraps the just
tool itself, drop those dependencies from the bootstrap process.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... in the same way, as we support different names for cc and c++.
|
|
... also in the first phases of the bootstrap procedure.
Co-authored-by: Oliver Reiche <oliver.reiche@huawei.com>
|
|
|
|
|
|
|
|
|
|
In particular, also add a target that explicitly all dependencies
besides python3 and the C++ compiler which also serves as a machine
checkable documentation.
|
|
For quick development, it is convenient to only need a C++ compiler
and python3 and get all dependencies downloaded at the beginning
of the bootstrap process. For packaging the tool, however, this
is not a valid approach; dependencies should be managed by the
packing tool there (so that security updates have to be fixed only
at one place). So, for building our tool, the dependencies look
like installed to the ambient environment.
|
|
|
|
|
|
... supporting trigger_on_parse() option, which allows to
call option functions multiple times, instead of collecting
the option values in a vector and processing this vector.
|
|
|
|
As our default (bundled) bootstrap brings a well defined version of
ssl, use this also in the initial bootstrap step.
|
|
Since in default (bundled) bootstrap, we bring our own version
of libgit2, also use that for the initial bootstrap step.
|
|
... so that they become fully content-fixed and we can benefit from
target caching, once implemented.
|
|
|
