[Swift] Support `swift_c_module` / Bazel swift modules

Open
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift
Domain
build-system

Research direction

Start by examining how XCHammer currently tests custom modules and handles modulemaps generated by Bazel. Compare the swift_c_module/Bazel module case with the existing custom-module behavior, and define done as correctly handling those modulemaps in generated Xcode projects while preserving the relevant tests.

Written by the indexing model from the issue text.

Description

XCHammer is tested on custom modules. The modulemaps generated in Bazel are somewhat of special case: consider how to handle these.

Dominant language
Swift
Stars
314
Forks
45
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bazel-xcode/xchammer

All issues in bazel-xcode/xchammer

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.