bazelbuild / bazelbuild/bazel

Using @import syntax on objc_library

Open
#9,429 5 comments 1 reaction 0 assignees View on GitHub
not stale P3 team-Rules-CPP type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

## Description of the problem / feature request:
Title

### Feature requests: what underlying problem are you trying to solve with this feature?
We have lots of Objc modules that also importing Swift codes. #6243 actually solves this issue but the progress went into limbo, so we are facing a quite big blocker right now.

Is there any relevant discussion regarding this? I can fork Bazel to support this, but this would be quite painful from maintenance perspective in the future if not officially supported.

### Have you found anything relevant by searching the web?
https://github.com/bazelbuild/bazel/pull/6243

Contributor guide

Open the contributing guide

Research direction

Start by reading the stalled pull request #6243 and comparing it with the objc_library behavior described here. Done means Bazel officially supports @import syntax for Objective-C modules that import Swift code, with the expected build behavior covered by the relevant tests identified during that investigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
objective-c, swift
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.