Files
meta-openembedded/meta-networking
Trevor Woerner 89e234d4bb c-ares: rely on cmake.bbclass to put cmake package files in dev package
The cmake.bbclass in oe-core now ensures that ${libdir}/cmake and
${datadir}/cmake end up in the dev package, so recipes no longer need to
provide custom packaging rules to handles these files.

	http://git.openembedded.org/openembedded-core/commit/?id=d91dc4666683a96e9d03cbbd21b8a546f9069c93

Originally-conceived-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-05-29 09:12:40 -07:00
..
2015-02-23 13:21:07 -05:00

meta-networking
===============

This layer is intended to be a central point for networking-related
packages and configuration.  It should be useful directly on top of
oe-core and compliments meta-openembedded.  It should be primarily useful
to the following groups:

      - Anyone building a small networking device (eg. a home router /
        bridge / switch).

      - Anyone wanting to add network services to their device (eg.
        anything that might benefit from a small ftp/tftp server)

Dependencies
------------

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: master
revision: HEAD

For some recipes, the meta-oe layer is required:

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe
branch: master
revision: HEAD

URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-python
branch: master
revision: HEAD

Maintenance
-----------

Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.