Skip to content

Conversation

@bkhouri
Copy link
Contributor

@bkhouri bkhouri commented Oct 27, 2025

relates to: #9287

@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 27, 2025

@swift-ci test

@bkhouri bkhouri force-pushed the t/main/gh9287_rdar163484107_command_line_feature_parity branch from 5951fe8 to 3ab4cbe Compare October 28, 2025 13:54
@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 28, 2025

@swift-ci test

@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 28, 2025

@swift-ci test windows

@bkhouri bkhouri force-pushed the t/main/gh9287_rdar163484107_command_line_feature_parity branch from 3ab4cbe to d7b534f Compare October 28, 2025 15:23
@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 28, 2025

@swift-ci test

@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 28, 2025

@swift-ci test windows

/// Which compile-time sanitizers should be enabled.
@Option(
name: .customLong("sanitize"),
help: "Turn on runtime checks for erroneous behavior, possible values: \(Sanitizer.formattedValues)."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this accidentally added from a different PR?

Copy link
Contributor Author

@bkhouri bkhouri Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was not. swift argument parser library lists the possible values, so the redundant text was removed.

.Feature.CommandLineArguments.Configuration,
),
.tags(
.Feature.CommandLineArguments.VeryVerbose,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tags feel very fine-grained and hard to individually maintain, should we use something more general?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tags are currently being used to determine command line feature parity between SwiftBuild and native build system.

.SWBINTTODO("Test fails because the dummy-swiftc used in the test isn't accepted by swift-build. This needs to be investigated"),
arguments: getBuildData(for: SupportedBuildSystemOnPlatform),
.tags(
.Feature.EnvironmentVariables.SWIFT_EXEC,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question here, I'm not 100% convinced tags for individual env vars makes sense

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would tend to agree, but we need to track the feature parity between native and SwiftBuild. This is one way to track which environment variables are added.

@bkhouri
Copy link
Contributor Author

bkhouri commented Oct 28, 2025

@swift-ci test self hosted windows

@bkhouri bkhouri enabled auto-merge (squash) October 28, 2025 19:13
@bkhouri bkhouri merged commit d9bcb45 into swiftlang:main Oct 28, 2025
6 checks passed
@bkhouri bkhouri deleted the t/main/gh9287_rdar163484107_command_line_feature_parity branch October 29, 2025 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants