diff options
| author | Alex Rønne Petersen <alex@alexrp.com> | 2024-10-08 08:14:11 +0200 |
|---|---|---|
| committer | Alex Rønne Petersen <alex@alexrp.com> | 2024-10-16 22:25:13 +0200 |
| commit | 140fb615a6a351fb397d6a538a4954a2229e90a8 (patch) | |
| tree | f1d3cfab015500387401b7fabdf58ab38e8edfb1 /lib/std/Build/Module.zig | |
| parent | bdb00b393e1910d30be04490535960651a7a07b7 (diff) | |
| download | zig-140fb615a6a351fb397d6a538a4954a2229e90a8.tar.gz zig-140fb615a6a351fb397d6a538a4954a2229e90a8.zip | |
std.Target: Move isLib{C,Cxx}LibName() to std.zig.target.
These are really answering questions about the Zig compiler's capacity to
provide a libc/libc++ implementation. As such, std.zig.target seems like a more
fitting place for these.
Diffstat (limited to 'lib/std/Build/Module.zig')
| -rw-r--r-- | lib/std/Build/Module.zig | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/std/Build/Module.zig b/lib/std/Build/Module.zig index 76d1bf8816..347695a4c0 100644 --- a/lib/std/Build/Module.zig +++ b/lib/std/Build/Module.zig @@ -492,11 +492,11 @@ pub fn linkSystemLibrary( const b = m.owner; const target = m.requireKnownTarget(); - if (target.isLibCLibName(name)) { + if (std.zig.target.isLibCLibName(target, name)) { m.link_libc = true; return; } - if (target.isLibCxxLibName(name)) { + if (std.zig.target.isLibCxxLibName(target, name)) { m.link_libcpp = true; return; } |
