Closed namark closed 2 years ago
The following links are available: build (ubuntu-18.04, full)
build (windows-2019, full)
The following links are available: build (macOS-10.15, client)
build (macOS-10.15, full)
build (ubuntu-18.04, full)
build (windows-2019, full)
The following links are available: build (macOS-10.15, full)
build (ubuntu-18.04, full)
build (macOS-10.15, client)
build (windows-2019, full)
The following links are available: build (macOS-10.15, full)
build (ubuntu-18.04, full)
build (macOS-10.15, client)
build (windows-2019, full)
The following links are available: build (macOS-10.15, client)
build (ubuntu-18.04, full)
The following links are available: build (macOS-10.15, client)
build (ubuntu-18.04, full)
build (macOS-10.15, full)
build (windows-2019, full)
The naming of files in /libraries/vircadia-client appears to be contrary to Vircadia conventions: starting with a lower case letter (convention is uppercase) and using "_"s in names (convention is upper camel case).
This is similar to function names, wanted to make the API interface stand out and be more C like, these again should not be included anywhere in the repo, other than the unit tests. The src/internal
folder has the C++ implementation details where I tried to follow our coding style, so there is some blending of styles going on between the two, but yeah in general I try to stick to C style in API interface (what will be exposed to the potential users) and our usual style in the implementation details.
The following links are available: build (macOS-10.15, client)
The following links are available: build (macOS-10.15, client)
build (ubuntu-18.04, full)
build (macOS-10.15, full)
build (windows-2019, full)
Builds upon https://github.com/vircadia/vircadia/pull/1623
The unit test will attempt to connect to localhost and send a message in "Chat" channel in appropriate JSON format, so it should appear in the Domain tab of the native interface chat, and otherwise it will test just a few error cases.