-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrading libopenmetaverse for RESTbot (legacy issue)
Note: This was a legacy issue that doesn't affect RESTbot anymore; RESTbot now uses LibreMetaverse, which is a fork of the currently unmaintained libopenmetaverse
, and which is available directly through Microsoft's package repositories. As such, it can be fully integrated into the build sequence in a standard way, and, as such, does not require a separate installation.
Nevertheless, if for some reason you really wish to build RESTbot linked to an obsolete version of libopenmetaverse
, then the following would apply to you:
RESTbot was designed to allow "easy" upgrade of libopenmetaverse
by having it on a separate directory. The problem is that libopenmetaverse
goes through several evolutions and it soon its API becomes incompatible with software developed for past versions
The instructions below assume Mac OS X or Linux. You're on your own if you're using Windows (sorry!).
- If you're using SVN: delete the
libopenmetaverse
folder under RESTbot and force a commit. - Go to a different directory and get the latest code from libopenmetaverse using:
svn co https://svn.github.com/openmetaversefoundation/libopenmetaverse libopenmetaverse
(see http://lib.openmetaverse.org/wiki/Download) - Now delete the SVN tags from libopenmetaverse (they will conflict with your build) by going to the freshly created
libopenmetaverse
and runningfind . -name '.svn' -print -exec rm -rf .svn {} \;
- Move this
libopenmetaverse
folder properly under RESTbot's own folder - Go to
libopenmetaverse
and do./runprebuild.sh nant
- Now commit the full changes on your SVN
Note: The above instructions need to be updated for using native Git commands as well as changing things to libremetaverse
instead (gwyneth 20211121)