文件列表:

.travis.yml (0, 2018-05-30)
3rdparty (0, 2018-05-30)
3rdparty\googletest (0, 2018-05-30)
CMakeLists.txt (3817, 2018-05-30)
LICENSE (1512, 2018-05-30)
cmake (0, 2018-05-30)
cmake\UtilFuns.cmake (390, 2018-05-30)
cmake\mrpt_vrep_bridgeConfigVersion.cmake.in (379, 2018-05-30)
cmake\mrpt_vrep_bridgeConfigVersion.hpp.in (253, 2018-05-30)
conversions (0, 2018-05-30)
conversions\CMakeLists.txt (39, 2018-05-30)
doc (0, 2018-05-30)
doc\CMakeLists.txt (1392, 2018-05-30)
doc\Doxyfile.in (106408, 2018-05-30)
models (0, 2018-05-30)
mrpt_graphslam_2d (0, 2018-05-30)
mrpt_graphslam_2d\CMakeLists.txt (1589, 2018-05-30)
mrpt_graphslam_2d\lua_scripts (0, 2018-05-30)
mrpt_graphslam_2d\lua_scripts\dummy (0, 2018-05-30)
mrpt_graphslam_2d\plugins (0, 2018-05-30)
mrpt_graphslam_2d\plugins\dummy (0, 2018-05-30)
mrpt_graphslam_2d\remoteApi (0, 2018-05-30)
mrpt_graphslam_2d\remoteApi\LICENSE (2015, 2018-05-30)
mrpt_graphslam_2d\remoteApi\bubbleRob_test.cpp (2018, 2018-05-30)
mrpt_graphslam_2d\test (0, 2018-05-30)
mrpt_graphslam_2d\test\runTests.cpp (129, 2018-05-30)
scenes (0, 2018-05-30)

# mrpt_vrep_bridge This package is a **work in progress**. Functionality advertised in the README file probably won't work or may be buggy. ## Description This repository provides packages and tools for interfacing the Mobile Robot Programming Toolkit ([MRPT](http://www.mrpt.org/)) with the V-REP robotics simulator. Following is a list of the functionalities that it provides: * TODO * TODO * ... ## Project layout: TODO - Describe the layout of each one of the libraries as well as the functionality of each one of its subdirectories ## Installation TODO ## Usage TODO ## Notes * Code targets exclusively the MRPT-2.x code. No backwards compatibility with MRPT 1.5 is provided. ## Demos TODO ## Contributing Code in the current repo abides to the same [guidelines as MRPT](https://github.com/MRPT/mrpt/blob/master/.github/CONTRIBUTING.md). On using the git VCS, do have the following bullet points in mind: 1. Separate subject from body with a blank line 2. Limit the subject line to 50 characters 3. Capitalize the subject line 4. Do not end the subject line with a period 5. Use the imperative mood in the subject line 6. Wrap the body at 72 characters 7. Use the body to explain what and why vs. how For more details about the desired style of git commit messages have a read at these articles: * https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message * https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html * https://chris.beams.io/posts/git-commit/

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：