Jorijn van der Graaf
7d93289201
42a2701 removed the depArgs declaration together with the --local
branch it fed, but the GitProject call that remained still passed
.args = depArgs. project.cpp stopped compiling, and with it every load
of this repository: crafter-build's own project.cpp pulls it in through
#pragma crafter dependency, so its build, lint and test runs fail as
soon as the clone is updated.
The call now passes no args. The test's crafter-build dependency only
needs the host defaults, and crafter-build is about to forward a
project's own args to its sibling projects by default anyway. The
comment above it still described the --local checkout the same commit
removed; it now says what the code does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
39 lines
1.9 KiB
C++
39 lines
1.9 KiB
C++
// SPDX-License-Identifier: LGPL-3.0-only
|
|
// SPDX-FileCopyrightText: Copyright (C) 2026 Catcrafts®
|
|
|
|
import std;
|
|
import Crafter.Build;
|
|
namespace fs = std::filesystem;
|
|
using namespace Crafter;
|
|
|
|
extern "C" Configuration CrafterBuildProject(std::span<const std::string_view> args) {
|
|
Configuration cfg;
|
|
cfg.path = "./";
|
|
cfg.name = "Crafter.LintRules";
|
|
cfg.outputName = "Crafter.LintRules";
|
|
cfg.type = ConfigurationType::LibraryStatic;
|
|
ApplyStandardArgs(cfg, args);
|
|
// No dependency on Crafter.Build, on purpose. The rules only ever run
|
|
// inside a crafter-build process, which provides the symbols, and a host
|
|
// build already sees the Crafter.Build modules through the PCM cache
|
|
// crafter-build keeps for its own project files — declaring the library
|
|
// here would make every consumer clone and build all of crafter-build
|
|
// just to lint.
|
|
std::array<fs::path, 1> ifaces = { "interfaces/Crafter.LintRules" };
|
|
std::array<fs::path, 0> impls = {};
|
|
cfg.GetInterfacesAndImplementations(ifaces, impls);
|
|
|
|
// The rule test compiles the module as its own interface and links
|
|
// crafter-build, from git, to run the linter in-process. Only when this
|
|
// is the project being built: crafter-build itself loads this file as a
|
|
// dependency, and the test's GitProject would then load crafter-build's
|
|
// project file again and recurse into the cycle guard. No target check:
|
|
// crafter-build only runs on Linux, and the hard-coded triple this used
|
|
// to compare against silently dropped the test on any host that spells
|
|
// its triple differently (the Flatpak's x86_64-unknown-linux-gnu).
|
|
if (IsTopLevelProject()) {
|
|
Configuration* build = GitProject({ .source = { .url = "https://forgejo.catcrafts.net/Catcrafts/Crafter.Build.git" } });
|
|
cfg.AddTest("HouseRules", ifaces).Dependencies({ build });
|
|
}
|
|
return cfg;
|
|
}
|