|author||Mike Frysinger <firstname.lastname@example.org>||Wed Apr 06 16:44:18 2016 -0400|
|committer||Mike Frysinger <email@example.com>||Wed Apr 06 20:56:26 2016 +0000|
clean up example/test_device clashes Move the duplicated libevhtp logic to third_party.mk so that multiple targets can rely on it being set up in the same way. Delete the duplicate example object rules from tests_schema.mk. We already include examples.mk before tests_schema.mk, so we know those rules are defined for us. We just need to depend on the output libs. Finally namespace the daemon variables in examples & tests_schema so they don't stop on each other in weird ways. Change-Id: I28fa152d8c8a30c84f7095e335e31a52889b5682 Reviewed-on: https://weave-review.googlesource.com/3152 Reviewed-by: Alex Vakulenko <firstname.lastname@example.org>
libWeave is the library with device side implementation of Weave protocol.
Sources are located in git repository at https://weave.googlesource.com/weave/libweave/
Make sure you have a bin/ directory in your home directory and that it is included in your path:
mkdir ~/bin PATH=~/bin:$PATH
Download the Repo tool and ensure that it is executable:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
mkdir ~/weave cd ~/weave repo init -u https://weave.googlesource.com/weave/manifest repo sync
This checks out libweave and its dependencies into the ~/weave directory.
|include/||Includes to be used by device code|
|examples/||Example of device code|
|Makefile, *.mk files||Build files|
sudo apt-get update sudo apt-get install \ autoconf \ automake \ binutils \ g++ \ hostapd \ libavahi-client-dev \ libcurl4-openssl-dev \ libevent-dev \ libexpat1-dev \ libnl-3-dev \ libnl-route-3-dev \ libssl-dev \ libtool
make --jobs/-j flag is encouraged, to speed up build time. For example
which happens to be the same as
make all -j
See the examples README for details.
In order to cross-compile, all you need to configure is CC/CXX/AR.
make CC=your-cc CXX=your-cxx AR=your-ar
So if you have a toolchain in a path like
make \ CC=/opt/vendor/bin/arm-linux-gcc \ CXX=/opt/vendor/bin/arm-linux-g++ \ AR=/opt/vendor/bin/arm-linux-ar
The build supports transparently downloading & using a few cross-compilers. Just add
cross-<arch> to the command line in addition to the target you want to actually build.
This will cross-compile for an armv7 (hard float) target:
make cross-arm all-libs
This will cross-compile for a mips (little endian) target:
make cross-mipsel all-libs
make test make export-test
The build supports using qemu to run non-native tests.
This will run armv7 tests through qemu:
make cross-arm testall
The Android Developing site has a lot of good tips for working with git and repo in general. The tips below are meant as a quick cheat sheet rather than diving deep into relevant topics.
Make sure to have correct user in local or global config e.g.:
git config --local user.name "User Name" git config --local user.email email@example.com
repo start <branch name> .
git commit -a -v
repo upload .
Go to the url from the output of
repo upload and add reviewers.