Lines Matching refs:will
194 # By default the result will be returned ready to be passed directly
344 # This test will match in case there are more generator expressions in the flag.
424 # the zephyr_library_* API then precedence will be given to the
467 # within Zephyr will be looked up.
536 # Linking with a dummy interface library will place flags later on
538 # zephyr_interface will be the first interface library that flags
576 "application mode. `${library}` will not be treated as a Zephyr library."
616 # An empty Zephyr library will generate a CMake
638 # files of this library will be accessible to the 'app' library.
653 # should exist for each interface_library and will determine if 'app'
766 # This macro is like board_set_runner(), but will only make a change
814 # The build system will then ensure the command line used to
825 # The build system tests for the existence of the macro and will
934 # The function will check the revision from `-DBOARD=<board>@<revision>` that
936 # When `EXACT` is not specified, this function will set the Zephyr build system
948 # board will be used. If both `EXACT` and `OPTIONAL` are given, then
955 # If `EXACT` is not provided, then closest lower revision will be selected
956 # as the active revision, which in the example will be `0.1.0`.
960 # user will be printed with an error if no revision is given
967 # that current board implementation will not work with board
969 # and user will be printed with an error if using
976 # will be used as a valid revision for the board.
1167 # check_compiler_flag, they will always pass, but -W<warning> can be
1188 # below and you will see that concurrent cmake processes created the
1234 # <files> is one or more .ld formatted files whose contents will be
1238 # Subsequent calls to zephyr_linker_sources with the same file(s) will remove
1268 # NOCACHE_SECTION, DTCM_SECTION or ITCM_SECTION the contents of the files will
1437 # The FILES directive will relocate a list of files (wildcards supported)
1438 # This directive will relocate file1. and file2.c to SRAM:
1443 # The LIBRARY directive will relocate a library
1444 # This directive will relocate the target my_lib to SRAM:
1597 # When MERGE is supplied a list of build strings will be returned with the full
1599 # The full order of build strings returned in the list will be:
1605 # If BUILD is supplied, then build type will be appended to each entry in the
1608 # with the sanitized revision string will be added in addition to the
1626 # <out-variable>: Output variable where the build string will be returned.
1627 # SHORT <out-variable>: Output variable where the shortened build string will be returned.
1637 # will return the string `alpha_debug` in `build_string` parameter.
1641 # will return the string `alpha_1_0_0_debug` in `build_string` parameter.
1645 # will return the string `alpha_soc_bar` in `build_string` parameter.
1649 # will return a list of the following strings
1654 # will return two lists of the following strings
1660 # will return the string `soc_bar_foo` in `build_string` parameter.
1884 # <keys> : output variable which will be populated with variable
1917 # target property will be unset.
1928 # Otherwise, the variable/property will be set to the provided value.
2412 # The dep file will contain `\` for line continuation.
2475 # with the extension that it will check that the linker supports the flag before
2519 # with the extension that it will set the property on both the compile and
2543 # with the extension that it will check that the compiler supports the flag
2548 # The 'SHELL:' prefix will be dropped before testing, so that
2598 # will print: "BOARD: nrf52dk"
2606 # will cause a FATAL_ERROR and print an error message if the first
2617 # will cause a FATAL_ERROR and print an error message if the first
2628 # will cause a FATAL_ERROR if there is no file or directory behind the
2671 # files are returned. Configuration files will be:
2675 # The conf file search will return existing configuration
2683 # BOARD_REVISION will be used, unless NAMES are
2688 # Only the first match found in <paths> will be
2695 # BUILD debug, will look for <board>_debug.conf
2700 # SUFFIX fish, will look for <file>_fish.conf and use
2701 # if found but will use <file>.conf if not found
2703 # must contain at least one element, else an error will be raise…
2983 # When using CMake version 3.20, the implementation will execute using CMake
3010 # This function will check the provied filename or list of filenames to see if they have a
3070 # The sanitized string will be returned in UPPER case.
3156 # this functions will return the var name in out var for the scope if it is
3157 # defined, else it will set the outvar to undefined.
3178 # is supplied, will return a list of found items. If REVERSE is supplied
3179 # together with MERGE, the order of the list will be reversed before being
3180 # returned. Reverse will happen before the list is returned and hence it will
3200 # If using MERGE then SYSBUILD GLOBAL will get both the local and global
3351 # previous zephyr_set() call. The value will be stored in the <output> var.
3379 # <value> : Value of variable, multiple values will create a list.
3415 # REQUIRED: Optional flag. If specified, then an unset <variable> will be
3429 # The value defined on the first CMake invocation will be stored in the CMake
3441 # If the user tries to change <variable> to a new value, then a warning will
3442 # be printed, and the previously cached value (CACHED_<variable>) will be
3461 # If user uses -D<variable>=<new_value>, then cli_argument will hold the new
3462 # value, otherwise cli_argument will hold the existing (old) value.
3559 # This functions will traverse the build tree, starting from <directory>.
3560 # It will read the `BUILDSYSTEM_TARGETS` for each directory in the build tree
3651 # names will be returned.
3801 # will make this clear in each case.
3822 # The node's path will be returned in the <var> parameter.
3823 # <var> will be undefined if node does not exist.
3825 # <var> : Return variable where the node path will be stored
3866 # # The variable 'path' will be left undefined for a nonexistent
3870 # The node's path will be returned in the <var> parameter. The
3871 # variable will be left undefined if the alias does not exist.
3873 # <var> : Return variable where the node path will be stored
3915 # The result of the check, either TRUE or FALSE, will be returned in
3918 # <var> : Return variable where the check result will be returned
3959 # The result of the check, either TRUE or FALSE, will be returned in
3962 # <var> : Return variable where the check result will be returned
4004 # Get a devicetree property value. The value will be returned in the
4022 # The property value will be returned in the <var> parameter if the
4024 # <var> will be undefined otherwise.
4045 # <var> : Return variable where the property value will be stored
4099 # Get a list of paths for the nodes with the given compatible. The value will
4101 # <var> will be undefined if no such compatible exists.
4106 # <var> : Return variable where the property value will be stored
4156 # The value will be returned in the <var> parameter.
4164 # <var> : Return variable where the property value will be stored
4193 # index 0 will be returned. Do not give both <idx> and <name>.
4195 # The value will be returned in the <var> parameter.
4205 # - <var> will be undefined if node does not exists or does not have a register
4208 # <var> : Return variable where the address value will be stored
4258 # index 0 will be returned. Do not give both <idx> and <name>.
4260 # The value will be returned in the <value> parameter.
4268 # <var> : Return variable where the size value will be stored
4344 # The result of the check, either TRUE or FALSE, will be stored in the
4379 # The node's path will be returned in the <var> parameter. The
4380 # variable will be left undefined if the chosen node does not exist.
4382 # <var> : Return variable where the node path will be stored
4532 # symbol __DTS__ will be defined. If the preprocessor command fails, a
4541 # These will, in effect, be concatenated in order
4759 # The section will only be defined if the devicetree exists and has status okay.
4807 # The memory will only be defined if the devicetree node or a devicetree node
4897 # section will be placed in, as that will be determined by the group setup.
4899 # Each group will define the following linker symbols:
4904 # Note: <name> will be converted to lower casing for linker symbols definitions.
4908 # If a group is used then the VMA region of that group will be used.
4921 # will create two groups in same memory region as groupB will inherit the LMA
4942 # will create groupB inside groupA:
5002 # will be configured. This section will default include input sections of the
5004 # This means the section named `foo` will default include the sections matching
5006 # Each output section will define the following linker symbols:
5011 # value will be identical to `__<name>_start`
5018 # If <group> is used here it means the section will use the
5019 # same VMA memory region as <group> but will not be placed
5023 # from SRAM base and offset, then the region defined by KVMA will
5025 # If <group> is used here it means the section will use the
5026 # same VMA memory region as <group> but will not be placed
5029 # If VMA is different from LMA, the code / data will be loaded
5033 # If <group> is used here it means the section will use the
5034 # same LMA memory region as <group> but will not be placed
5042 # ENDALIGN <alignment>: Align the end so that next output section will start aligned.
5045 # in identical way. For example the Scatter file will align both load and
5047 # NOINPUT : No default input sections will be defined, to setup input
5051 # Default a section will be present during all linker passes
5146 # Define an output section which will set up an iterable area
5148 # Input sections will be sorted by name in lexicographical order.
5150 # Each list for an input section will define the following linker symbols:
5154 # The output section will be named `<name>_area` and define the following linker
5160 # value will be identical to `__<name>_area_start`
5166 # If VMA is different from LMA, the code / data will be loaded
5177 # in identical way. For example the Scatter file will align both load and
5235 # will create an input section matching `.z_init_PRE_KERNEL_1?_` and
5240 # will be sorted.
5293 # using priority Zephyr CMake linker will create sections
5295 # sections will internally be given a CMake process order
5360 # `+, -, *` and similar. The expression will go directly into the
5361 # linker, and all `@<symbol>@` will be replaced with the referred
5389 # The macro will create a list of argument-value pairs for defined arguments
5398 # will create a list as: "FOO;bar;QUX;TRUE" which can then be parsed as argument
5419 # A FATAL_ERROR will be raised if not one of the required arguments has been
5435 # A FATAL_ERROR will be raised if not one of the required arguments has been
5453 # A FATAL_ERROR will be raised if not one of the required arguments has been
5478 # A FATAL_ERROR will be raised if one of the required arguments is missing.
5495 # A FATAL_ERROR will be raised if any of the arguments are given together.
5510 # A FATAL_ERROR will be raised if any of the flags are given together.
5583 # The llext code will be compiled with mostly the same C compiler flags used
5602 # will compile the source file src/llext/hello_world.c to a file
5705 # they will take care of this and the default copy is replaced by a no-op.
5797 # Add a custom command to an llext target that will be executed during
5798 # the build. The command will be executed at the specified build step and
5811 # Anything else after COMMAND will be passed to add_custom_command() as-is
5878 # expressions that will be used to exclude flags from the input list.
5880 # The resulting generator expression will be stored in the variable <outvar>.