Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[build.ps1] build swift-lmdb using cmake #77562

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

matthewbastien
Copy link
Member

This is tracked by rdar://139431575 as a part of swiftlang/vscode-swift#562

Build swift-lmdb on Windows using newly added cmake files in the repository. This change makes it so that IndexStoreDB uses the same version of LMDB as swift-docc and enables SourceKit-LSP to use swift-docc as a dependency to fulfill documentation requests on behalf of the VS Code Swift extension.

@matthewbastien
Copy link
Member Author

@matthewbastien
Copy link
Member Author

utils/build.ps1 Outdated
@@ -2439,6 +2439,17 @@ function Test-Format {
}
}

function Build-LMDB() {
Build-SPMProject `
Copy link
Member

Choose a reason for hiding this comment

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

Should this be Build-CMakeProject? This doesn't match the commit message. Do you have numbers for what the toolchain size impact is on static vs dynamic builds?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch! Admittedly I'm quite new to this and haven't been able to compile Swift on Windows at all. So, I don't have those numbers right now.

@matthewbastien
Copy link
Member Author

3 similar comments
@matthewbastien
Copy link
Member Author

@matthewbastien
Copy link
Member Author

@matthewbastien
Copy link
Member Author

utils/build.ps1 Outdated
-Bin (Get-HostProjectBinaryCache LMDB) `
-Arch $Arch `
-Platform Windows `
-UseBuiltCompilers C `
Copy link
Member

Choose a reason for hiding this comment

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

Is there a reason to use clang-cl instead of cl here?

Copy link
Member Author

Choose a reason for hiding this comment

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

No particular reason. I've updated this patch to use the same approach you took in #71422.

One question about that PR: how close is it to being able to merge? I realize that the next step of this will probably be to get a cmake build of swift-docc working since the goal is to use swift-docc as a dependency to SourceKit-LSP which currently has a cmake build.

@matthewbastien
Copy link
Member Author

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