> For the complete documentation index, see [llms.txt](https://sdk.twelite.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.twelite.info/en/twelite-sdk-howto/birudonitsuite/makefile-nitsuite.md).

# About Makefile

The source code and other definitions to be built are written in the Makefile.

| TWELITE                          | Specify the model to be built, BLUE for TWELITE BLUE (TWE-001 Lite) or RED for TWELITE RED.                                                                                                                                |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| PROJNAME                         | Decide the name of the generated file. If not specified, use. If not specified, the `../..` folder name will be used.                                                                                                      |
| APPSRC                           | Specify the file to be compiled, using the `+=` operator, as in `APPSRC+=test.c`.                                                                                                                                          |
| TARGET\_TYPE                     | Specify the target to generate. When `TARGET_TYPE = bin` is specified, the target is an executable, and when `TARGET_TYPE = a` is specified, the target is a library.。                                                     |
| TOCONET\_DEBUG                   | If 1, include the debug code for the stack. The output file name will be prefixed with `_TDBG`. See the API description for the stack debug code. 0 means do not include it, and the binary size will be slightly smaller. |
| CFLAGS                           | Add gcc options at compile time. Use the `+=` operator, like `CFLAGS += -DMY_DEBUG`. Do not specify any optimization options, as they are predefined.                                                                      |
| APP\_COMMON\_SRC\_DIR\_ADD1 .. 4 | Specify the search path for source and header files. Liks as `APP_COMMON_SRC_DIR_ADD1 = ... /mydir`, relative to the folder where the Makefile is located.                                                                 |
| INCFLAGS                         | If you want to specify additional include folders only, use relative paths like `INCLFAGS == -I.../mydir` to specify a relative path.                                                                                      |
| ADDITIONAL\_LIBS                 | Specify additional libraries (`.a`) to be linked, like `ADDITIONAL_LIBS += . /mylib.a`.                                                                                                                                    |
| ADDITIONAL\_OBJS                 | Specify additional object files (.o) to be linked, like`ADDITIONAL_OBJS += ../myobj.o`.                                                                                                                                    |
| LDLIBS                           | Specify the compiler libraries (math, spp, etc.) by adding `LDLIBS += m`. In this specification, -lm is passed to the linker.                                                                                              |
| LDFLAGS                          | Additional options to the linker can be specified as `LDFLAGS += -u dummy`. The options required by TWELITE are pre-defined.                                                                                               |
| OBJDIR\_SUFF                     | Include the string set in the object storage folder name.                                                                                                                                                                  |
| TARGET\_SUFF                     | Include the string you set in the target (.bin) file name.                                                                                                                                                                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sdk.twelite.info/en/twelite-sdk-howto/birudonitsuite/makefile-nitsuite.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.