admin/opensim-libs
1
0
Fork 0
mirror of git://opensimulator.org/git/opensim-libs synced 2026-08-14 00:58:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

update readme

Browse Source
This commit is contained in:
UbitUmarov
2024-04-10 18:54:42 +01:00
parent 4f44c63250
commit 2e75b6849e
2 changed files with 14 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+14
View File
@@ -0,0 +1,14 @@
This is a code repository containing various 3rd party library packages used by opensim (as version >= 0.9.3).
Opensim does not use Nuget (and hopefuly never will)
OpenSim checks out with most of these libs precompiled in the bin folder.
In the case of managed code, these will be .dll assemblies compiled to run on dotnet platform.
In the case of unmanaged (native) code, like C/C++ libs with, most native libraries will be placed in folder bin/lib64.
Since 0.9.3.0 32bit is no longer supported, so folder bin/lib32 alternative place was removed.
Most opensim project will need proper load code and a corresponding projectName.dll.config file setup so the runtime can load the correct native library for the runtime platform and cpu
see for example `bin/OpenMetaverse.dll.config` on opensim source.
A few cases may use other arrangement
README.txt
-8
View File
@@ -1,8 +0,0 @@
this is a code repository containing (hopefully) up-to-date versions of various 3rd party library packages used by opensim.
OpenSim checks out with most of these libs precompiled in the /bin folder. In the case of managed code, these will be .dll assemblies that run on any .net/mono platform. In the case of unmanaged (native) code, ie C/C++ libs with .NET wrappers (ODE, SQlite, openjpeg), there will typically be a *.net.dll wrapper, which invokes either a native .dll (on windows), or a native shared library (.so, on unix). The binaries shipping in opensim are compiled on windows Vista and Ubuntu 7.04, in a 32-bit x86 environment. Other operating systems and hardware setups may require you to recompile the libraries and manually copy them to your ./bin folder. Alternatively, you may want to get certain packages from other sources (such as a distribution management system), install them in places like SYSTEM32 (win32) or /usr/local/lib.
Another reason to use this code is to update, patch, debug, and potentially add features to the native code. Note that anything other than minor build patches would constitute a fork from the project in question; such a decision should be made in communion with the community (unless you're doing this for yourself and never plan to contribute it back, in which case blah! to you)
-danx0r, 10/19/07