wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Andrej Mihajlov <and@mullvad.net>
To: Alexey Ponkin <alexey.ponkin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuardKit iOS - Import package and usage of 'Shared' classes
Date: Tue, 22 Mar 2022 12:50:12 +0100	[thread overview]
Message-ID: <49AF0CB9-0474-40D2-813B-4B1C22CB8161@mullvad.net> (raw)
In-Reply-To: <CA+QYBNn=ObJGz04je7a36VQnWNdGjn20LjsG04KDOmxzZA_oqA@mail.gmail.com>

Hi,

The source code under Sources/Shared is a part of WireGuard app. These files are checked out by SPM, because both WireGuardKit and WireGuard app share the same repository. However, these files aren’t part of WireGuardKit and thus not available for direct import via WireGuardKit.

Best,
Andrej

> On 20 Mar 2022, at 16:24, Alexey Ponkin <alexey.ponkin@gmail.com> wrote:
> 
> Hi guys,
> I'm trying to use WiregurdKit in my iOS app. I imported the package as
> described here - https://github.com/WireGuard/wireguard-apple. Now I
> can use `PacketTunnelProvider` inside `WireGuardNetworkExtension`. But
> unfortunately , I can't use any classes and extensions from the
> `Shared` folder
> (https://github.com/WireGuard/wireguard-apple/tree/master/Sources/Shared).
> Is there any way to make them 'visible' for my project? I'm fairly new
> to Swift and iOS development. I would like, for instance, to reuse
> this extension (https://github.com/WireGuard/wireguard-apple/blob/master/Sources/Shared/Model/NETunnelProviderProtocol%2BExtension.swift)
> and may be, `Keychan` wrapper class.
> Thanks in advance for your help.


      reply	other threads:[~2022-03-22 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 15:24 WireGuardKit iOS - Import package and usage of 'Shared' classes Alexey Ponkin
2022-03-22 11:50 ` Andrej Mihajlov [this message]

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=49AF0CB9-0474-40D2-813B-4B1C22CB8161@mullvad.net \
    --to=and@mullvad.net \
    --cc=alexey.ponkin@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).