From: Andrej Mihajlov <and@mullvad.net>
To: Houman <houmie@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard-apple 1.0.16-27 can’t be added via SPM
Date: Thu, 5 Oct 2023 11:28:03 +0200 [thread overview]
Message-ID: <C5E4F9F5-D489-4250-890A-3DE50ED09BE8@mullvad.net> (raw)
In-Reply-To: <CABBZOs=zEFGfLERL=JC1KtbZTka+1EitTHH9ZEdwkU95BYEHyA@mail.gmail.com>
Hi Houman,
I maintain a fork of wireguard-apple for the past couple of years and it works with Xcode 15 and Swift 5.9:
github.com/mullvad/wireguard-apple (branch: mullvad-master)
In the app I maintain, WireGuardGoBridge target is built using bash script for flexibility, instead of bash sorcery so you might want this too:
github.com/mullvad/mullvadvpn-app/blob/main/ios/build-wireguard-go.sh <http://github.com/mullvad/mullvadvpn-app/blob/main/ios/build-wireguard-go.sh>
Hope any of this helps.
Best,
Andrej
> On 4 Oct 2023, at 18:04, Houman <houmie@gmail.com> wrote:
>
> Hello Andrej,
>
> Thank you for your reply. I have already forked the branch and set
> Package.swift to swift-tools-version:5.5. But I still get the same
> error as before.
>
> Swift-tools-version:5.5 only worked with the previous version
> 1.0.15-26 that was released on 23rd Sep 2021.
> The 1.0.16-27 that was tagged on 15th Feb 2023 is completely broken
> and doesn't work with SPM. I have tried swift-tools-versions 5.6,
> 5.7, 5.8 and 5.9. I strongly believe that this commit from Jason
> ccc7472fd7d1c7c19584e6a30c45a56b8ba57790 on 14th Feb 2023 has broken
> it. I don't think he tested it afterwards with SPM.
>
> This (outdated) PR proves that more people are having problems with
> installing the latest version since the February release:
> https://github.com/WireGuard/wireguard-apple/pull/24
>
> Error Message:
> Invalid manifest (compiled with: "/Applications/Xcode
> app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/us/bin/swift",
> "visoverlay", "/ar/folders/9m/lwx244892997kpg7vb5vssh0000gn/T/TemporaryDirectory.
> BBHXP8/vfs.yaml*, "-", "/Applicationscode.
> app/Contents/SharedFrameworks/SwiftM.framework/SharedSupport/ManifestA*,
> "PackageDescription, "-Xlinker", "-rath", "-Xlinker", "/Applicatio..
>
> Xcode version: Version 15.0 (15A240d)
> Mac version: 14.0 (23A344)
>
> Your help is much appreciated,
> Thanks,
> Houman
>
>
> On Wed, 4 Oct 2023 at 12:46, Andrej Mihajlov <and@mullvad.net> wrote:
>>
>> Hi,
>>
>> Right. I think that preamble in Package.swift should be changed from:
>>
>>> // swift-tools-version:5.3
>>
>> to at least:
>>
>>> // swift-tools-version:5.5
>>
>> Which works with Xcode 15 based on my experience.
>>
>> Jason could you please bump it?
>>
>> Best,
>>
>> Andrej
>>
>>> On 30 Sep 2023, at 21:09, Houman <houmie@gmail.com> wrote:
>>>
>>> Hello Jason, Andrej
>>>
>>> Please try to add the latest Wireguard-Apple 1.0.16-27 via Swift
>>> Package Manager and you will see that fails. The issue could be
>>> related to swift-tools-version.
>>>
>>> Please advise what to do?
>>> Thank you.
>>> Houman
>>
next prev parent reply other threads:[~2023-10-05 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 19:09 Houman
2023-10-04 11:46 ` Andrej Mihajlov
2023-10-04 16:04 ` Houman
2023-10-05 9:28 ` Andrej Mihajlov [this message]
2023-10-05 10:08 ` Houman
2023-10-05 10:35 ` Andrej Mihajlov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C5E4F9F5-D489-4250-890A-3DE50ED09BE8@mullvad.net \
--to=and@mullvad.net \
--cc=houmie@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).