Skip to content

Commit 9eecae6

Browse files
committed
Update README for new platforms
Platform compatibility for both server and client has been updated. Server runs under x86, x64 Windows EXE, and x86, x64, ARM64 and ARMv7 Linux. Unix Server builds were introduced in b31, and cross-compilation was fixed by build 33. Client iOS was already available when Android was compatible, as iOS used same raw (Lacewing Relay UTF-8) protocol as Android and Windows. Client HTML5/UWP was introduced in build 33, and fixed compatibility with Firefox in build 34. Clients can be from Windows ANSI, Windows Unicode, Android, iOS, HTML5, UWP - latter two using secure or insecure WebSocket over Lacewing Relay protocol.
1 parent 148d27a commit 9eecae6

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

README.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,29 @@
11
# bluewing-cpp-server
22
An example of Lacewing Blue (Bluewing) implementation of Lacewing Relay protocol as a server.
3-
Windows EXE using Visual Studio. Full C++ speed, with no trace of Clickteam Fusion.
4-
3+
Windows EXE and Unix executable using Visual Studio. Full C++ speed, with no trace of Clickteam Fusion.
4+
Windows EXE is in x86 and x64. Unix is in x86 (i386), x64 (x86_64), ARMv7 and ARM64.
5+
6+
57
# Features
68
* This server is compatible with clients that use Lacewing Relay protocol.
79
* Optional Flash policy hosting, and auto-generates a policy file for the Lacewing port.
810
* Optional upload cap on TCP + UDP for all clients, and TCP for clients.
11+
* This server is compatible with HTML5 and UWP JavaScript, both secure and insecure WebSocket.
12+
To use the WebSocket Secure server, ensure you have privkey.pem and fullchain.pem in the app folder.
913

10-
This server is NOT compatible with HTML5. There is no HTML5 server for Lacewing as of this writing, so it is not compatible.
1114

1215
# This server's Fusion client compatibility
1316
The server is compatible with any of the following (and any combination):
1417
* non-Fusion clients
1518
* client programs that are made in Clickteam Fusion 2.5 or Multimedia Fusion 2.0
16-
* Fusion 2.0/2.5 clients for Windows, Android, and SWF/Flash
19+
* Fusion 2.0/2.5 clients for Windows, Android, iOS, SWF/Flash, HTML5, and UWP
1720
* Lacewing Relay and Lacewing Blue Fusion extensions (Blue is highly recommended for client, as it is more recent)
1821

1922
# Tools needed to edit this source
2023
You will need Visual Studio 2017+, with Windows XP support add-on.
2124
* To add it to your VS install, run the Visual Studio Installer, select More > Modify, and under Individual Components tab, enable C++ Windows XP Support for VS 2017 (v141) tools.
2225
(Note that VS 2017 XP is the latest XP, so you want VS 2017 XP support even if you're using VS 2019.)
23-
* Alternatively, XP support requirement can be removed in half a minute; simply switch the compiler under Project Properties > General > Platform Toolset, from v141_xp to v121 (if you're using VS 2017) or v141 (if VS 2019).
26+
* Alternatively, XP support requirement can be removed in half a minute; simply switch the compiler under Project Properties > General > Platform Toolset, from v141_xp to v121 (if you're using VS 2017) or to v141 (if VS 2019).
2427

2528
Due to use of C++17 features, like std::string_view, VS 2015 is not supported.
2629

0 commit comments

Comments
 (0)