> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/ida-actions/setupcompiler.md).

# SetupCompiler

## Description

Setup target compiler and its parameters. This dialog allows the user to specify the compiler used to create the program along with the memory model, default calling convention, ABI and other parameters. Please note that while some combinations of the parameters are meaningless, IDA doesn't check them for validity. It is up to the user to specify a correct combination.

IDA tries to determine the correct values automatically.

The include directories are a list of directories that look for the standard C headers. This parameter is used during parsing C header files (the Parse C header file... command; action `LoadHeaderFile`). The directories must be separated by ';' in MS Windows and ':' in Linux. The predefined macros field has the same format and is used similarly. Please note that IDA doesn't define any compiler-specific macros by default.

### Include directories

The include directories can be edited as the usual single line, or — after a click on the chevron next to the field — in a small editor holding one directory per line:

![Include directories, collapsed](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-fb738e9e66cdaac80ed5f2e6382b33179fa753c6%2Fclang-parser-options.png?alt=media)

![Include directories, expanded](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-f2823a94412dc3773edbf590fddfdeb1f2ea8836%2Finclude-dirs-expanded.png?alt=media)

Collapsing the editor (or accepting the dialog while it is open) recomposes the single line, using the platform's path separator.

### Source parser

Type declarations are parsed by the clang-based parser, which understands C, C++, Objective-C and Objective-C++ out of the box. The **Source parser** group of the **Compiler options** dialog shows the active parser and its command-line arguments (with ready-made presets for common targets); hovering the parser shows the languages it supports.

![Compiler - Parser options](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-9450ea01fb29da0518c8d27441fec1dce165088a%2Fcompiler-parser.png?alt=media)

Other parsers can be selected from the dropdown if needed:

* **clang** - the default parser (based on LLVM)
* **legacy** - old internal IDA parser (deprecated, will be removed in future versions)

### Parser Configuration

The parser can be fine-tuned in its own options dialog, opened by the **Configure ...** button next to it.

![Parser specific options](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-3ebbd358629c112f4283ed767daa1c73b627790d%2Fparser-options.png?alt=media)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/ida-9.5/ida-actions/setupcompiler.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.