cinderblocks/LibreMetaverse.Typesv2.2.3.909
✓ Verified.NET 8.0.NET 9.0.NET Std2.0
LibreMetaverse type library
Get Started
$ dotnet add package LibreMetaverse.TypesReadme
▄▄▌ ▪ ▄▄▄▄· ▄▄▄ ▄▄▄ .• ▌ ▄ ·. ▄▄▄ .▄▄▄▄▄ ▄▄▄· ▌ ▐·▄▄▄ .▄▄▄ .▄▄ · ▄▄▄ .
██• ██ ▐█ ▀█▪▀▄ █·▀▄.▀··██ ▐███▪▀▄.▀·•██ ▐█ ▀█ ▪█·█▌▀▄.▀·▀▄ █·▐█ ▀. ▀▄.▀·
██▪ ▐█·▐█▀▀█▄▐▀▀▄ ▐▀▀▪▄▐█ ▌▐▌▐█·▐▀▀▪▄ ▐█.▪▄█▀▀█ ▐█▐█•▐▀▀▪▄▐▀▀▄ ▄▀▀▀█▄▐▀▀▪▄
▐█▌▐▌▐█▌██▄▪▐█▐█•█▌▐█▄▄▌██ ██▌▐█▌▐█▄▄▌ ▐█▌·▐█ ▪▐▌ ███ ▐█▄▄▌▐█•█▌▐█▄▪▐█▐█▄▄▌
.▀▀▀ ▀▀▀·▀▀▀▀ .▀ ▀ ▀▀▀ ▀▀ █▪▀▀▀ ▀▀▀ ▀▀▀ ▀ ▀ . ▀ ▀▀▀ .▀ ▀ ▀▀▀▀ ▀▀▀
LibreMetaverse
LibreMetaverse is a fork of libOpenMetaverse which in turn was a fork of libSecondLife, a library for developing Second Life-compatible virtual world clients. LibreMetaverse returns the focus to up-to-date Second Life and OpenSim compatibility with an eye to performance, multi-threading, and memory management.
The canonical source for LibreMetaverse can be found at: https://github.com/cinderblocks/libremetaverse
Simple installation procedure
Windows
The dotnet utility is cross-platform so compilation is no different than on Linux/macOS.
You may, however, opt to use Visual Studio as you would any other .NET application.
Linux/macOS
-
Make sure you have at least
dotnetinstalled, with a valid SDK and runtime of at least .NET6 available! -
From the root, run
dotnet restore LibreMetaverse.Release.sln. You should get some errors regarding missing Windows libraries; that's ok, you can ignore those, they're to be expected since Linux/macOS do not include such libraries. Some test applications are Windows-only.
If all goes well, you should now have all dependent packages properly installed. -
From the root, run
dotnet msbuild LibreMetaverse.Release.sln, and enjoy the superfast Roslyn compiler at work 😄 It should finish after a few minutes, depending on the speed of your machine. -
Your binaries will be under
../bin/net8.0or../bin/net9.0(there might be a few more directories under../bin), depending on what runtimes you have installed on your system. Make sure you to the correct directory depending on the runtime you have, and then search for all your binaries there: they should be normal-looking executable files (with the attribute set) and having the name of the appropriate test application (e.g. for the interactive testing tool).
