File: ImageScaleFactorsInputFileGroupingStrategy.swift

package info (click to toggle)
swiftlang 6.2.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,856,264 kB
  • sloc: cpp: 9,995,718; ansic: 2,234,019; asm: 1,092,167; python: 313,940; objc: 82,726; f90: 80,126; lisp: 38,373; pascal: 25,580; sh: 20,378; ml: 5,058; perl: 4,751; makefile: 4,725; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (48 lines) | stat: -rw-r--r-- 3,318 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
//===----------------------------------------------------------------------===//
//
// This source file is part of the Swift open source project
//
// Copyright (c) 2025 Apple Inc. and the Swift project authors
// Licensed under Apache License v2.0 with Runtime Library Exception
//
// See http://swift.org/LICENSE.txt for license information
// See http://swift.org/CONTRIBUTORS.txt for the list of Swift project authors
//
//===----------------------------------------------------------------------===//

public import SWBCore
import SWBUtil

// FIXME: Presently we have no good way during grouping to detect whether we're matching a single file against tiffutil or multiple files against tiffutil.  In principle we could handle that in FilesBasedBuildPhaseTaskProducer once all grouping is completed.  But at present this is handled in a hackier manner in TiffUtilToolSpec.constructTasks() - see the FIXME comment therein for more about this.
//
/// A grouping strategy that groups image files containing scale factors of the form "@<n>x" at the end of their base names.
@_spi(Testing) public final class ImageScaleFactorsInputFileGroupingStrategy : InputFileGroupingStrategy {

    /// Name of the tool to which the grouping strategy belongs (used as a part of the returned group identifier).
    let toolName: String

    @_spi(Testing) public init(toolName: String) {
        self.toolName = toolName
    }

    public func determineGroupIdentifier(groupable: any InputFileGroupable) -> String? {
        // Work with the path without the '.extension'.  Note that this is the full path without the extension, not just the basename of the last path component.
        // Note that we always end up including the suffix in the identifier, since we don't want to group files of different types together in the same command.
        let path = groupable.absolutePath
        let pathWithoutSuffix = path.withoutSuffix

        // This logic walks backwards over the end of the path-without-extension looking for the '@<n>x' marker.  If it at any point determines there isn't such a marker then it returns the original path.  If it does find the marker, then it returns the path without the marker.
        var idx = pathWithoutSuffix.endIndex
        guard idx > pathWithoutSuffix.startIndex else { return "tool:\(toolName) file-base:\(path.str)" }
        idx = pathWithoutSuffix.index(before: idx)
        guard pathWithoutSuffix[idx] == "x" else { return "tool:\(toolName) file-base:\(path.str)" }
        guard idx > pathWithoutSuffix.startIndex else { return "tool:\(toolName) file-base:\(path.str)" }
        idx = pathWithoutSuffix.index(before: idx)
        guard pathWithoutSuffix[idx] == "1" || pathWithoutSuffix[idx] == "2" || pathWithoutSuffix[idx] == "3" else { return "tool:\(toolName) file-base:\(path.str)" }
        guard idx > pathWithoutSuffix.startIndex else { return "tool:\(toolName) file-base:\(path.str)" }
        idx = pathWithoutSuffix.index(before: idx)
        guard pathWithoutSuffix[idx] == "@" else { return "tool:\(toolName) file-base:\(path.str)" }
        guard idx > pathWithoutSuffix.startIndex else { return "tool:\(toolName) file-base:\(path.str)" }
        return "tool:\(toolName) file-base:\(pathWithoutSuffix[pathWithoutSuffix.startIndex..<idx])\(path.fileSuffix)"
    }
}