CPSwarm Communication Library

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro jazzy showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro kilted showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro rolling showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro ardent showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro bouncy showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro crystal showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro eloquent showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro dashing showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro galactic showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro foxy showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro iron showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro lunar showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro jade showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro indigo showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro hydro showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro melodic showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange

No version for distro noetic showing kinetic. Known supported distros are highlighted in the buttons above.

swarmros package from swarmros repo

swarmros

ROS Distro
kinetic

Package Summary

Tags	No category tags.
Version	0.3.6
License	Apache 2.0
Build type	CMAKE
Use	RECOMMENDED

Repository Summary

Checkout URI	https://github.com/amilankovich-slab/swarmros.git
VCS Type	git
VCS Version	master
Last Updated	2020-04-01
Dev Status	DEVELOPED
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

SwarmIO communications bridge for ROS

Additional Links

Website

Maintainers

Ákos Milánkovich

Authors

No additional authors.

CPSwarm Communication Library

The CPSwarm Communication Library provides a unified interface that tools and swarm members can use to interact with each other.

Getting started

For more information, see the WIKI.

Deployment

Packages are built continuously with Bamboo.

Build

Building on Linux

Build should work on any Linux distribution, but packaging and architecture detection will only work on Debian and Ubuntu. By default, everything is compiled for the host architecture, but cross-compilation is available. Currently armhf and arm64 are supported if the required tools are available. The default compiler is clang, but GCC can also be used. Builds were tested with Ubuntu 16.04 and 18.04, with all the latest updates installed.

There are three build modes you can choose from:

 - DEVELOPMENT (default)

Development mode will build and install all components into one subdirectory under the build directory. Useful when an IDE needs a full include path and for debugging. By default, products are installed into the “devtree-" subdirectory.

 - PACKAGE

Package mode will build .deb packages for each target - and set /opt/swarmio as the install prefix. Find the packages under the “packages” subdirectory.

 - INSTALL

Install will install all outputs onto the local machine, by default under /opt/swarmio.

To build, create a new directory outside the source tree, and issue the following commands inside it:

 cmake <PATH TO SOURCE> [optional parameters]
 cmake --build .

Optional parameters:

 -DSWARMIO_BUILD_MODE=<MODE> (DEVELOPMENT, PACKAGE or INSTALL)

Specifies build mode (see above). DEVELOPMENT build will generate debug executables, while PACKAGE and INSTALL builds will compile with release flags (and debug symbols).

 -DCMAKE_BUILD_TYPE=<TYPE> (Debug, Release, RelWithDebInfo)

Override build type derrived from build mode. See CMake docs for more info.

 -DCMAKE_INSTALL_PREFIX=<PATH>

Overrides the installation directory. For DEVELOPMENT and INSTALL build, this will override the output directory. For PACKAGE builds, it will override the installation prefix of the generated packages.

 -DSWARMIO_TARGET_ARCHITECTURE=<ARCH> (armhf or arm64)

Enables cross-compilation - required tools must already be installed. On Ubuntu systems, crossbuild-essential- packages should do the trick.

 -DSWARMIO_BUILD_ROS_NODE=ON

If turned on, swarmros will be built.

 -DSWARMIO_MULTISTRAP_CONFIGURATION=<CONFIG>

If configured, a full multistrap sysroot will be initialized before cross-compilation. Requires multistrap and a bunch of other tools to be installed. Currently supported configurations:

xenial (Ubuntu 16.04)
xenial-ros (Ubuntu 16.04 with ROS Kinetic Kame)
bionic (Ubuntu 18.04)
bionic-ros (Ubuntu 18.04 with ROS Melodic Morenia)

-DSWARMIO_SYSROOT=<SYSROOT PATH>

If multistrap is not used, a sysroot needs to be manually set for cross-compilation to work. Ensure that the system image contains no absolute symbolic links before using it.

File truncated at 100 lines see the full file

CHANGELOG

Changelog for package swarmros

Forthcoming

Update rules.em
Contributors: Ákos Milánkovich

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps	Name
	roscpp
	rosconsole
	std_msgs
	roslib

System Dependencies

Name
git
clang
multistrap
g++-5-arm-linux-gnueabihf
g++-5-multilib
cmake

Dependant Packages

Name	Deps
cpswarm_msgs
area_division
target_monitor

Launch files

No launch files found

Messages

Services

No service files found

Plugins

No plugins found.

Recent questions tagged `swarmros` at Robotics Stack Exchange