Repository navigation
[pigeon] Allow multiple output locations for generated Swift #164297
Description
Use case
When using Swift for iOS and macOS, it would be nice to be able to specify both folders as output locations.
Proposal
For example:
@ConfigurePigeon(PigeonOptions(
dartOut: 'lib/messages.g.dart',
swiftOut: ['ios/Classes/Messages.g.swift', 'macos/Classes/Messages.g.swift'],
))
Reacted by Abdelaziz Mahdy, JetA2 and kjxbyz
Activity
stuartmorgan-g commentedon Feb 27, 2025
Could you provide more information about the specific use case for sharing the Pigeon definition, but not the implementation (via
darwin/)?JifScharp commentedon Feb 28, 2025
I actually started out using
/darwin, because the original implementation was supposed to be the same for iOS and macOS. However, due to the native libraries involved, the actual implementation diverged heavily, until I split them up.So an implementation that uses a native library where the implementation is different for iOS and macOS, or potentially where different libraries are required for iOS and macOS.
darshankawar commentedon Mar 27, 2025
Sorry for coming back late on this issue, as I didn't see this issue in my list to address.
I'll keep the issue open for team's tracking.
stuartmorgan-g commentedon Apr 1, 2025
In our own implementations we generally would have different Pigeon files for fundamentally different implementations, but for the more traditional plugin style of having a single cross-platform interface as the language boundary, multiple output locations would be reasonable.
stuartmorgan-g commentedon Aug 31, 2026
@tarrinneal It turns out this is blocking for switching the
createtemplate to Pigeon, because the template generation allows for generatingios/andmacos/without generatingdarwin/, and there's currently no way to make that template work with Pigeon.If we don't want the value type to be variable, we could instead make a SwiftOptions entry for a secondary output location.
[pigeon] add support for multiple swift outputs (#12720)
[pigeon] add support for multiple swift outputs (flutter#12720)
[pigeon] add support for multiple swift outputs (flutter#12720)
github-actions commentedon Sep 23, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.