mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-08 08:02:45 +00:00
46c5f12a1f
A complete rewrite of the Overview section. The revised text provides a more logical and comprehensive introduction to the main concepts and capabilities of Zephyr, without providing an excessive level of detail. (Those details should be provided by the remaining sections of the Kernel Primer.) This rewrite has also resulted in some small changes to the About Zephyr and other Kernel Primer sections. Change-Id: Idd4d5e0f0aabaaee8cd43d12563018ba4d8f7417 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
41 lines
1.4 KiB
ReStructuredText
41 lines
1.4 KiB
ReStructuredText
.. _application_fundamentals:
|
|
|
|
Application Fundamentals
|
|
########################
|
|
|
|
A Zephyr application is defined by creating a directory containing the
|
|
following files.
|
|
|
|
* Application source code files
|
|
|
|
An application typically provides one or more application-specific files,
|
|
written in C or assembly language. These files are usually located in a
|
|
sub-directory called :file:`src`.
|
|
|
|
* Kernel configuration files
|
|
|
|
An application typically provides a configuration file (:file:`.conf`)
|
|
that specifies values for one or more kernel configuration options.
|
|
If omitted, the application's existing kernel configuration option values
|
|
are used; if no existing values are provided, the kernel's default
|
|
configuration values are used.
|
|
|
|
A microkernel application typically provides an additional microkernel
|
|
definitions (MDEF) file (:file:`.mdef`) that defines all of the system's
|
|
public microkernel objects. This file is not used with a nanokernel-only
|
|
application.
|
|
|
|
* Makefile
|
|
|
|
This file typically contains a handful of lines that tell the build system
|
|
where to find the files mentioned above, as well as the desired target
|
|
platform configuration and kernel type (either microkernel or nanokernel).
|
|
|
|
Once the application has been defined it can be built using a single command.
|
|
The results of the build process, including the final application image,
|
|
are located in a sub-directory called :file:`outdir`.
|
|
|
|
For additional information see:
|
|
|
|
* :ref:`application`
|