zephyr

History

Flavio Santes e669d10599 samples/static_lib: Add testcase.ini Add testcase.ini file for qemu_x86. We detected an unexpected behavior in sanitycheck before submitting this patch: In testcase.ini, if platform_whitelist contains more than one platform only the last platform will work. So, here we just use qemu_x86. However, we believe this situation is caused by the structure of this sample. See mylib/Makefile. Jira: ZEP-621 Change-Id: I656c1b9a69b93fd9f7b0d98a69f49b9641918a93 Signed-off-by: Flavio Santes <flavio.santes@intel.com>		2016-08-04 18:31:12 +00:00
..
hello_world	samples/static_lib: Linking with a static library	2016-07-01 00:39:20 +00:00
mylib	Makefile.toolchain.zephyr: Test CONFIG_TOOLCHAIN_VARIANT robustly.	2016-08-04 18:31:12 +00:00
Makefile	samples/static_lib: Add testcase.ini	2016-08-04 18:31:12 +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