media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration : 0 / 0 |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
fkie_potree_rviz_plugin | |
rviz |
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | hydro-devel |
Last Updated | 2013-08-15 |
Dev Status | MAINTAINED |
CI status | No Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Dave Hershberger
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Wiki Tutorials
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
fkie_potree_rviz_plugin | |
rviz |
Launch files
Messages
Services
Plugins
Recent questions tagged media_export at Robotics Stack Exchange
media_export package from media_export repomedia_export |
|
Package Summary
Tags | No category tags. |
Version | 0.2.0 |
License | BSD |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros/media_export.git |
VCS Type | git |
VCS Version | indigo-devel |
Last Updated | 2014-03-25 |
Dev Status | MAINTAINED |
CI status | Continuous Integration : 0 / 0 |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- William Woodall
Authors
- Dave Hershberger
media_export
This empty package exists to allow ROS packages to export media paths to each other.
The inspiration has been OGRE media paths, but the system could be used for any system that needs paths to be exported.
In practice, all one needs to do to export a path is something like this: (in rosbuild, put this in the manifest.xml)
<depend package="media_export"/>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
In a catkin package, put this in the package.xml:
<run_depend>media_export</run_depend>
<export>
<media_export ogre_media_path="${prefix}/Media/materials/scripts:${prefix}/Media/textures"/>
</export>
Then on the command-line you can do
rospack plugins --attr=ogre_media_path media_export
to see all the ogre_media_paths exported by all packages in your current ROS environment.
The export attribute is named “ogre_media_path” instead of just “path” because there may be media paths for other software libraries than Ogre, and it would be a waste to mix them all together.
The first use of media_export is for Ogre meshes which reference Ogre material scripts. These can be loaded both by rviz and by other code which processes URDF files.
Changelog for package media_export
0.2.0 (2014-03-24)
- set myself (william) as maintainer
- Contributors: William Woodall
0.1.0 (2013-08-15)
- fixed catkin_project() -> catkin_package()
- initial commit
- Contributors: Dave Hershberger
Wiki Tutorials
Dependant Packages
Name | Deps |
---|---|
fkie_potree_rviz_plugin | |
rviz |