diff options
| author | Klaus Aehlig <klaus.aehlig@huawei.com> | 2024-06-26 11:34:04 +0200 |
|---|---|---|
| committer | Klaus Aehlig <klaus.aehlig@huawei.com> | 2024-06-26 12:49:50 +0200 |
| commit | 70a854c2ce90194a943b6e007a1515dfc87314eb (patch) | |
| tree | 34cdae35fad3505c89a30edba0afddbebcf30382 /src | |
| parent | 8605d5cfe1043d41703ea8ca2604aace1d4d747c (diff) | |
| download | justbuild-70a854c2ce90194a943b6e007a1515dfc87314eb.tar.gz | |
just: shorten repeated mentioning of the top-level target
The build tool prints status messages at the end of each of the
major stages that sequentially follow each other. This allows,
in particular when using log files (that contain time stamps) to
quickly identify which phase was the resource consuming one. All
these message mention the (same!) configured target that is process
by this invocation of the build tool. In the presence of toolchains,
the configuration can, however, get quite large (containing lots of
paths to various tools). Therefore, shorted the configuration in the
repeated menions if it is very long (currenlty 320 characters); as
we do not change the first mentinoing ("Requested target is ..."),
even with that shortening the log contains the same information.
Diffstat (limited to 'src')
| -rw-r--r-- | src/buildtool/main/main.cpp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/buildtool/main/main.cpp b/src/buildtool/main/main.cpp index f107e38f..5a8b0bcf 100644 --- a/src/buildtool/main/main.cpp +++ b/src/buildtool/main/main.cpp @@ -1053,7 +1053,7 @@ auto main(int argc, char* argv[]) -> int { #ifndef BOOTSTRAP_BUILD_TOOL Logger::Log(LogLevel::Info, "Analysed target {}", - result->id.ToString()); + result->id.ToShortString()); { auto cached = stats.ExportsCachedCounter(); @@ -1093,7 +1093,7 @@ auto main(int argc, char* argv[]) -> int { result->modified ? fmt::format(" input of action {} of", *(result->modified)) : "", - result->id.ToString()); + result->id.ToShortString()); auto build_result = traverser.BuildAndStage(artifacts, |