LGTM, Samuli.
-Original Message-
From: Simon Rozman
Sent: Tuesday, October 16, 2018 3:26 AM
To: openvpn-devel@lists.sourceforge.net
Subject: [Openvpn-devel] [PATCH 3/5] Define _WIN32_WINNT=_WIN32_WINNT_VISTA in
MSVC
This makes MSVC and MinGW build environments more alike.
---
Hi Simon,
This approach keeps 'goes in DLL' next to the function itself, which I like. If
you're interested, another possible approach here is to use .DEF files with
MSVC, which can also do symbol aliasing:
https://docs.microsoft.com/en-us/cpp/build/exporting-from-a-dll-using-def-files
I would
Hi Simon,
This is painful to read, and I bet it was even more painful to write. I am
sorry it came to this, though it does look like it should(TM) work.
>From what I gather, the OS version should be checked in the
CustomAction's MSI execution conditions instead of in the CustomAction
itself.
Samuli, LGTM.
-Original Message-
From: Simon Rozman
Sent: Tuesday, October 16, 2018 3:26 AM
To: openvpn-devel@lists.sourceforge.net
Subject: [Openvpn-devel] [PATCH 5/5] Detect TAP interfaces with root-enumerated
hardware ID
This patch extends the TAP interface enumerating to detect
This looks pretty straightforward to me.
-Original Message-
From: Simon Rozman
Sent: Tuesday, October 16, 2018 3:26 AM
To: openvpn-devel@lists.sourceforge.net
Subject: [Openvpn-devel] [PATCH 1/5] Set output name to libopenvpnmsica.dll in
MSVC builds too
On MinGW builds, the Libtool
Am 08.11.18 um 13:31 schrieb milovan bjelogrlic:
> hi OpenVPN developers,
>
> Could you please provide me with information if there is place with
> documentation which contains API reference, code implementation
> documentation and any othed kinf of(good :)) documentation. I am
> interested in
