Closed kylefmohr closed 2 years ago
Thank you for bringing this up, this is good to know. Can I ask what version of macOS and Xcode you're using?
Sure thing, I'm running macOS 12.4 and Xcode Version 13.4.1 (13F100)
Did you clone the repo with git clone
, or did you download the files as a zip from GitHub? I think that local Swift Package Manager packages don't work if they're not under version control
Just double-checked, I did a git clone (--recursive, but don't think that matters) of airmessage-server
That's interesting, I did a test on my computer where cloning the repository would have Zlib come up automatically as a build scheme, whereas downloading the zip file would cause it to only have AirMessageTests.
It's possible I've installed something on my computer that I don't know about. In any case, thanks again for reporting this!
Let me run it back one more time and test again, it’s very possible it’s something minor I messed up. One sec.
On Jul 20, 2022, at 4:57 PM, Cole Feuer @.***> wrote:
That's interesting, I did a test on my computer where cloning the repository would have Zlib come up automatically as a build scheme, whereas downloading the zip file would cause it to only have AirMessageTests.
It's possible I've installed something on my computer that I don't know about. In any case, thanks again for reporting this!
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
@kylefmohr Just want to follow up, were you able to test this? If not, no worries!
Oh sorry to leave you hanging! I didn't have a chance to test it, I will close the issue, I'm sure it was something on my end. Thanks for following up, AirMessage has been incredibly helpful for me recently! So nice to be able to use iMessage/SMS from my Windows computers.
When I tried to build server and (I believe) followed the requisite setup instructions, the build fails due to the fact that it can't locate the zlib dependency. I was able to workaround this by:
I'm very new at Xcode/MacOS development, so I'm unsure how/if this is fixable from a project configuration standpoint, but I just wanted to document the steps in case anybody else ran into this as well.