SwiftLintPlugin execution from Script Build Phase

[frankois944]

When using the plugin from SPM, it's possible to run the switlint binary directly in the Script Build Phase, just like any other command.
The script locates the binary path and executes the command.

Sound like the CocoaPods integration.

I just added the script in the README and using the default value (xcode 15/16), these values can be wrong in previous xcode version or with custom package path.

SWIFT_PACKAGE_DIR="${BUILD_DIR%Build/*}SourcePackages/artifacts"
SWIFTLINT_CMD=$SWIFT_PACKAGE_DIR/swiftlintplugins/SwiftLintBinary/SwiftLintBinary.artifactbundle/swiftlint-*/bin/swiftlint

if test -f $SWIFTLINT_CMD 2>&1
then
    $SWIFTLINT_CMD
else
    echo "warning: `swiftlint` command not found - See https://github.com/realm/SwiftLint#installation for installation instructions."
fi

[SimplyDanny]

An interesting and nifty way to get to a versioned binary. 👍

However, it's probably not sure if this will work with future Xcode versions. Perhaps, we should also add a warning that this approach might fail with changes in Xcode.

[frankois944]

However, it's probably not sure if this will work with future Xcode versions. Perhaps, we should also add a warning that this approach might fail with changes in Xcode.

Yes, I know, it's possible, if Xcode change again the project package path, but for now, it's working on the version 15 and 16.

We can replace this static path by a command to automatically find the binary, but i'm not a fan to execute it every time...

[SimplyDanny]

However, it's probably not sure if this will work with future Xcode versions. Perhaps, we should also add a warning that this approach might fail with changes in Xcode.

Yes, I know, it's possible, if Xcode change again the project package path, but for now, it's working on the version 15 and 16.

We can replace this static path by a command to automatically find the binary, but i'm not a fan to execute it every time...

Well, then we should mention exactly that: works in Xcode 15 and 16, but no guarantee for other versions or an alternative path.

[frankois944]

However, it's probably not sure if this will work with future Xcode versions. Perhaps, we should also add a warning that this approach might fail with changes in Xcode.

Yes, I know, it's possible, if Xcode change again the project package path, but for now, it's working on the version 15 and 16.
We can replace this static path by a command to automatically find the binary, but i'm not a fan to execute it every time...

Well, then we should mention exactly that: works in Xcode 15 and 16, but no guarantee for other versions or an alternative path.

Ok, I added this message.

The SWIFTLINT_CMD path use the default Xcode configuration and has been tested on Xcode 15/16, in case of another configuration like custom Swift package path, please change the values accordinaly.

Understand, I'm using the default Xcode values. The user must adapt his configuration.