search

OpenDDS / meta-opendds

Open Embedded Layer for the OpenDDS package
Other
7 stars 4 forks source link

readme

This README file contains information on the contents of the meta-opendds layer.

Please see the corresponding sections below for details.

Dependencies

URI: git://git.openembedded.org/meta-openembedded branch: scarthgap

URI: https://git.yoctoproject.org/git/poky/meta branch: scarthgap

Patches

Please submit any patches against the meta-opendds layer via the pull-request mechanism on github.

Maintainer: Keith Derrick keith.derrick@lge.com

Table of Contents

I. Adding the meta-openembedded/meta-oe and meta-opendds layers to your build II. Misc

I. Adding the meta-openembedded/meta-oe and meta-opendds layers to your build

Run 'bitbake-layers add-layer meta-openembedded/meta-oe' Run 'bitbake-layers add-layer meta-opendds'

II. Misc

The layer contains two recipes for OpenDDS: one versioned and one not.

If PREFERRED_VERSION is not specifed in your local.conf then the OpenDDS 3.29.1 recipe will be selected for build by default

The versioned recipe will use the DOC Group ACE/TAO v2 by default. To build the versioned recipe with DOC Group ACE/TAO v3 add the following to your local.conf

PACKAGECONFIG:remove:pn-opendds = " doc-group2"
PACKAGECONFIG:remove:pn-opendds-native = " doc-group2"
PACKAGECONFIG:append:pn-opendds = " doc-group3"
PACKAGECONFIG:append:pn-opendds-native = " doc-group3"

Or to build with Doc Group ACE/TAO v4:

PACKAGECONFIG:remove:pn-opendds = " doc-group2"
PACKAGECONFIG:remove:pn-opendds-native = " doc-group2"
PACKAGECONFIG:append:pn-opendds = " doc-group4"
PACKAGECONFIG:append:pn-opendds-native = " doc-group4"

The unversioned recipe is provided to allow clients, via a bbappend, to build - for example - the HEAD of the master branch or some other version.

To use this unversioned recipe, add the following to your local.conf or distro configuration file.

PREFERRED_VERSION_opendds="1.0+git%"
PREFERRED_VERSION_opendds-native="1.0+git%"
PREFERRED_VERSION_nativesdk-opendds="1.0+git%"

Note that simply providing a different branch and SRCREV may be insufficient. If your desired commit is significantly newer than that used for the versioned recipe, then the generic build instructions may be insufficient or incorrect.