Skip to content

Conversation

@compnerd
Copy link
Member

We explicitly build cmark-gfm as static. This adjusts the usage to ensure that the module knows that the cmark that it is building against is static. This fixes a number of linker warnings on Windows.

We explicitly build cmark-gfm as static. This adjusts the usage to
ensure that the module knows that the cmark that it is building against
is static. This fixes a number of linker warnings on Windows.
@compnerd
Copy link
Member Author

@swift-ci please test

Copy link
Contributor

@QuietMisdreavus QuietMisdreavus left a comment

Choose a reason for hiding this comment

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

🚢

@QuietMisdreavus QuietMisdreavus merged commit e62a44f into swiftlang:main Jan 30, 2025
2 checks passed
@compnerd compnerd deleted the static branch January 30, 2025 17:41
@tonyarnold
Copy link

This change now means that we can't use the project as a dependency within Xcode:

the target 'Markdown' in product 'Markdown' contains unsafe build flags

@dlskawns96
Copy link
Contributor

I’m also running into the same issue when trying to depend on swift-markdown from an iOS project in Xcode.
As mentioned, SwiftPM rejects the package with:

the target 'Markdown' in product 'Markdown' contains unsafe build flags

To address this, I opened #239 describing the problem, and submitted PR #240 that guards the unsafeFlags behind a Windows-only conditional, so that non-Windows consumers are unaffected.

It would be great to get feedback on whether that approach makes sense to merge.

/cc @compnerd @QuietMisdreavus

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.

4 participants