Robot Operating System (ROS) is a meta-operating system for your robot.
It provides several services for a robot control system, including but
not limited to:
* language-independent and network-transparent communication
* hardware abstraction
* low-level device control
* implementation of commonly-used functionality
* message-passing between processes
* package management
* visualizers
This port provides the core part of ROS: the base system and the tools
to develop additional nodes. These additional nodes can be installed
manually or via the Ports Collection.
WWW: http://www.ros.org/wiki/ros
new devel/pkgconf added to replace devel/pkg-config. new version of pkg-config
are no more self hosting so we are stuck with 0.25 version while pkgconf provide
the same set of features as 0.27 and a compatible frontend. A symlink to
pkg-config has been added for convenience and compatibility
This also introduces a new macro to use pkgconf in your ports:
USE_PKGCONFIG
it can take the following arguments:
- yes (meaning build only dep)
- build (meaning build only dep)
- run (meaning run only dep)
- both (meaning run and build dep)
From now USE_GNOME= pkgconfig is deprecated in favour of USE_PKGCONFIG
The old gnome macro has been modified to use pkgconf but still the sameway: run
and build dep to avoid large breakage.
While here fix some ports relying on pkg-config but not specifying it, fix some
ports broken because testing wrong .pc files, and fix ports using pkg-config
--version to determine pkg-config version instead of
pkg-config --modversion pkg-config like recommanded by pkg-config
With Hat: portmgr
Exp-runs by: bapt (pointhat-west), beat (pointyhat)
For the ports that are maintained by ports@ that have pkgconfig as their
only USE_GNOME feature, convert to a BUILD_DEPENDS. This avoids both the
bug of the bogus run depend introduced by bsd.gnome.mk, and also avoids
needlessly pulling that file in.
Upgrade the Robot Operating System ports to their 1.4 aka Diamondback versions.
Detailed changelists are available on the WWW sites.
Port changes:
- distribution files are now fetched from upstream servers instead of
using local copies from my server
- Python files are now always compiled (to .pyc and .pyo) and use Python 2.7
- devel/ros is now split in to devel/ros, devel/ros-documentation,
devel/ros-rx, and devel-ros-comm to allow more lightweight installations
- Connect latter 3 ports to the build
- Add dependency on devel/cppunit, it is specified in rosdep.yaml and at
least devel/ros-common uses it.
- Perform all inline editing in post-patch target
- Don't move libraries to PREFIX/lib but symlink them there, some Python
modules depend on the libraries in their original location
- Remove instructions for manual installation, this is advanced stuff
- Silent pkg_delete warnings by explicitly creating all directories
- No need to patch download location in patch-gtest
- Bump PORTREVISION
- Move the core ros files from PREFIX/ros to PREFIX/ros/ros, this is
necessary to be able to upgrade add-on packages (like ros_tutorials) in
place due to the way rosmake searches for packages.
- Update ros/pkg-descr and ros_tutorials to reflect this
- Partially fix build with Clang (ros does not link yet)
- Makefile cleanups for devel/ros
- Bump PORTREVISIONs
- Upgrade the built-in googletest to 1.5.0
- Use ${WRKSRC}/googletest_backup instead of /var/tmp as a temporary backup
directory if dealing with an googletest installed from ports
- Add a stacks directory, which will be used as a destination for other
ROS packages
- Improve pkg-message
- Bump PORTREVISION
- Cleanups
- Properly fetch all required files in the fetch phase, and feed them to the
upstream build system. Since multiple files are fetched now, move all
distfiles to DIST_SUBDIR.
- Re-enable cluster build.
- Return pointy hat to pool.
Tested with: offline laptop doing 'make'
Blames: fast connection to upstream site and
too summarized upstream build logs.
Robot Operating System (ROS) is a meta-operating system for your robot.
It provides several services for a robot control system, including but
not limited to:
* language-independent and network-transparent communication
* including hardware abstraction
* low-level device control
* implementation of commonly-used functionality
* message-passing between processes
This port provides the core part of ROS: the base system and the tools
to develop additional nodes. These additional nodes can be installed
manually by using something like:
% svn co `roslocate svn nodename` nodename
(or git clone `roslocate svn nodename` nodename)
% rosmake nodename
WWW: http://www.ros.org/wiki/
