:orphan:

.. title:: CONFIG_BUILD_OUTPUT_EFI

.. kconfig:: CONFIG_BUILD_OUTPUT_EFI

CONFIG_BUILD_OUTPUT_EFI
#######################

*Build as an EFI application*

Type: ``bool``

Help
====

.. code-block:: none

    Build as an EFI application.

    This works by creating a "zephyr.efi" EFI binary containing a zephyr
    image extracted from a built zephyr.elf file.  EFI applications are
    relocatable, and cannot be placed at specific locations in memory.
    Instead, the stub code will copy the embedded zephyr sections to the
    appropriate locations at startup, clear any zero-filled (BSS, etc...)
    areas, then jump into the 64 bit entry point.

Direct dependencies
===================

\ :kconfig:`X86_64 <CONFIG_X86_64>`

*(Includes any dependencies from ifs and menus.)*

Default
=======

- n

Kconfig definition
==================



At ``Kconfig.zephyr:423``

Included via ``Kconfig:8``

Menu path: (Top) → Build and Link Features → Build Options

.. code-block:: kconfig

    config BUILD_OUTPUT_EFI
    	bool "Build as an EFI application"
    	default n
    	depends on X86_64
    	help
    	  Build as an EFI application.
	  
    	  This works by creating a "zephyr.efi" EFI binary containing a zephyr
    	  image extracted from a built zephyr.elf file.  EFI applications are
    	  relocatable, and cannot be placed at specific locations in memory.
    	  Instead, the stub code will copy the embedded zephyr sections to the
    	  appropriate locations at startup, clear any zero-filled (BSS, etc...)
    	  areas, then jump into the 64 bit entry point.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*