Lines Matching full:files

36 - A "project" is a directory that contains all the files and configuration to build a single "app" …
42 …ar pieces of standalone code which are compiled into static libraries (.a files) and linked into a…
81 …run, this directory will contain interim object files and libraries as well as final binary output…
85 …lso include ``Kconfig.projbuild`` and ``Makefile.projbuild`` files, which are special files for `o…
104 - ``PROJECT_NAME``: Name of the project. Binary output files will use this name - ie myProject.bin,…
151 - All source files in the same directory as the makefile (``*.c``, ``*.cpp``, ``*.cc``, ``*.S``) wi…
157 …for a component to have no `component.mk` file, if it only contains other files which influence th…
168 …h of a directory inside `$(BUILD_DIR_BASE)` where this component's source files are to be built. T…
201 …nent-relative paths to files which should trigger a re-link of the ELF file if they change. Typica…
213 …t directory, which will be added to the include search path for this component's source files only.
214 …DES``: Any extra include paths used when compiling the component's source files. These will be pre…
215 …files (``*.cpp``, ``*.c``, ``*.S``). Defaults to '.', ie the component directory itself. Override …
216 …files to compile. Default value is a .o file for each source file that is found in ``COMPONENT_SRC…
217 - ``COMPONENT_EXTRA_CLEAN``: Paths, relative to the component build directory, of any files that ar…
219 …`KConfig.projbuild`` and/or ``Makefile.projbuild`` files to configure the project, but no source f…
221 - ``CPPFLAGS``: Flags passed to the C preprocessor (used for .c, .cpp and .S files). A default set …
223 - ``COMPONENT_ADD_LDFRAGMENTS``: Paths to linker fragment files for the linker script generation fu…
238 To create a component KConfig file, it is easiest to start with one of the KConfig files distribute…
262 - `Makefile.projbuild` files from components are included into the make process, to add extra targe…
272 …cludes all component ``Makefile.componentbuild`` files, making any recipes, variables etc in these…
275 …d, default build and clean targets are created for the component's source files and the prerequisi…
278 …hrough the ``component_wrapper.mk`` file and some of the ``component.mk`` files included with esp-…
298 … size information about the app. ``make size-components`` and ``make size-files`` are similar targ…
331 …eeds to add to CFLAGS for the entire project (not just for its own source files) then you can set …
333 ``Makefile.projbuild`` files are used heavily inside esp-idf, for defining project-wide build featu…
342 This is an equivalent to ``Makefile.projbuild`` for `component configuration` KConfig files. If you…
349 …files from other files, it is necessary to be able to add recipes, macros or variable definitions …
354 Some special components which contain no source files, only ``Kconfig.projbuild`` and ``Makefile.pr…
374 This will compile all source files in the src1/ and src2/ sub-directories instead.
378 Specifying source files
381 The standard component.mk logic adds all .S and .c files in the source directories as sources to be…
393 The configuration system can be used to conditionally compile some files depending on the options s…
406 …list of object files as parameters. If the condition is true (in this case: if the BAR feature is …
441 …will only work when all object files for a component are named explicitely, and will not clean up …
471 You can set a variable COMPONENT_EMBED_FILES in component.mk, giving the names of the files to embe…
484 …inary prefix in the symbol name is added by objcopy and is the same for both text and binary files.
486 …example_file:`protocols/http_server/file_serving/main/component.mk` - two files are loaded at buil…
491 …its code and data will be placed in memory through linker fragment files. These files are processe…
535 …ome glue in the components/bootloader/Makefile.projectbuild file. See these files for more details.