zephyr

History

Daniel Thompson 560afde9c3 build: Document outputexports In addition to providing documentaton, we also modify the static_lib example to use outputexports instead of the double-include Makefile.toolchain trick. For this to work well we need to fix a tiny bug in the dependency handling in Makefile.inc. Change-Id: I6571bc681bc34155f37cff1eccc2ea12ed52ef07 Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>		2016-11-12 02:08:08 +00:00
..
hello_world	build: Document outputexports	2016-11-12 02:08:08 +00:00
mylib	build: Document outputexports	2016-11-12 02:08:08 +00:00
Makefile	build: Document outputexports	2016-11-12 02:08:08 +00:00
README	samples/static_lib: Linking with a static library	2016-07-01 00:39:20 +00:00
prj.conf	samples/static_lib: Add testcase.ini	2016-08-04 18:31:12 +00:00
testcase.ini	samples/static_lib: Add testcase.ini	2016-08-04 18:31:12 +00:00

README

Linking with a static library
#############################

This sample shows how to link a static library to a Zephyr application.
A sample library is also included.

Read mylib/Makefile to discover how to use the Zephyr's toolchain
to build a static library.

If the library's source code is available, perhaps it could be more
easier to integrate that source code to your application than creating
the static library.


Build instructions
==================

1. It is assumed that ZEPHYR_GCC_VARIANT and ZEPHYR_SDK_INSTALL_DIR
variables are already set. See:

https://www.zephyrproject.org/doc/getting_started/getting_started.html

2. source $ZEPHYR/zephyr-env.sh

   Where $ZEPHYR points to the directory that contains the zephyr
   repository.

3. make

4. make run