Refactor mjVFS and resource management.
Resource operations (e.g. mju_openResource, mju_readResource, and mju_closeResource, etc.) are now all handled by a VFS instance. It is now up to the VFS to determine which provider to use in order to handle those operations. This allows us to dynamically add/remove (aka "mount") providers to a VFS to handle special requests. mj_addFileVFS and mj_addBufferVFS have been reimplemented as two such use-cases. Moreover, we expose the mounting behaviour with two new functions: mj_mountVFS and mj_unmountVFS. PiperOrigin-RevId: 861550939 Change-Id: I070eb4bcc2982466c8f368f7918005538baa5185
This commit is contained in:
committed by
Copybara-Service
parent
e977b0d660
commit
0ddbb46fa1
@@ -1357,6 +1357,25 @@ The VFS must first be allocated using :ref:`mj_defaultVFS` and must be freed wit
|
||||
|
||||
Initialize an empty VFS, :ref:`mj_deleteVFS` must be called to deallocate the VFS.
|
||||
|
||||
.. _mj_mountVFS:
|
||||
|
||||
`mj_mountVFS <#mj_mountVFS>`__
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. mujoco-include:: mj_mountVFS
|
||||
|
||||
Mount a ResourceProvider to handle file operations under the given path; return 0: success,
|
||||
2: repeated name, -1: invalid resource provider.
|
||||
|
||||
.. _mj_unmountVFS:
|
||||
|
||||
`mj_unmountVFS <#mj_unmountVFS>`__
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. mujoco-include:: mj_unmountVFS
|
||||
|
||||
Unmount a previously mounted ResourceProvider; return 0: success, -1: not found in VFS.
|
||||
|
||||
.. _mj_addFileVFS:
|
||||
|
||||
`mj_addFileVFS <#mj_addFileVFS>`__
|
||||
|
||||
Reference in New Issue
Block a user