-
Notifications
You must be signed in to change notification settings - Fork 104
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
Library Does Not Support Installation Via Swift Package Manager #1387
Comments
I've got a working POC of this at https://github.com/thedavidharris/sdl_ios/tree/spm-support just adding some modulemaps to build bson in place with some symlinks, but there are a few caveats:
If you want @joeljfischer I can continue plugging away at some of these, but that folder structure problem I didn't want to work out without consulting the team. |
Hi @thedavidharris, thanks for looking into this more. There's been an open issue for a long time to move the project to have public and private files in separate folders. That does eventually need to happen, we just keep putting it off. I think it would be a necessary part of having official SPM support.
This seems to be a legacy file from when the quick testing library needed it. I deleted it locally and ran the tests and they seemed to work fine now. That could be removed.
These are necessary because without them the lock screen won't work. I know that support for that is coming in Xcode 12, but I haven't looked deeper into it. |
All that sounds good. I'd agree that addressing #568 is a pre-requisite. After that, this should be able to flow through and still export the packages correctly, with the resources once Xcode 12 comes, so gives a little time. What would be the ideal folder structure for the project? Something that mirrors the virtual folders in Xcode today but one layer deeper in public/private? |
I think that the folder structure would just be public and private, not mirroring the Xcode virtual folder structure. I worry that with additional public / private below the virtual structure it would get too messy and difficult to maintain. |
@thedavidharris Hello, #568 has been fixed and closed. Did you want to submit a PR for this? If so, there's a deadline of it being merged on 09/18, so we would need the PR submitted by 09/11, and you would need to be responsive to the PR review to get it done by our release deadline. Otherwise, I can take it on and fix it. If I do, do you mind if I re-use the work you did on that branch? |
Hey @joeljfischer , apologies been out for a few weeks. Likely won't get a chance to pick this up myself the next couple weeks (and our teams don't need any SPM support in the near-term), so if you're up for it definitely good to re-use some of this work. |
Bug Report
Currently, the library does not support installation via Swift Package Manager due to SPM's inability to resolve submodules see here for more info. We will have to move the submodule code into the library.
Reproduction Steps
Expected Behavior
The imported package works correctly
Observed Behavior
The imported package fails to work correctly due to failures around the BSON lib.
OS & Version Information
The text was updated successfully, but these errors were encountered: