> 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/core/flirt/how-tos/generate-flirt-signatures-from-libraries.md).

# Generate FLIRT signatures from libraries

```
 Action    name: makesig:create_signature
 
```

This command generates a FLIRT signature file. It is available via **File → Produce file → Create SIG file...**. A function is eligible when the name doesn't start with `sub_`.

```
 File: Pathname for the signature file
 Library name: identifier, shown in the description of Signature

 Collect functions
  - All: Generate signature for all functions in the idb that are eligible
  - Selected: Generate a signature only for the selection in Functions

 Collisions
  - Ignore: don't add collision FLIRT signature
            will delete the Exclusion file if it exists
  - Deal with manually: if there is collisions, a window will open to manage
                        the collisions
```

Two or three files are generated:

| File           | Description                                                                                                  |
| -------------- | ------------------------------------------------------------------------------------------------------------ |
| Signature file | The output file                                                                                              |
| Pattern file   | Filename is Signature filename with extension replaced with "pat"                                            |
| Exclusion File | Filename with extension replaced by "exc". Only present if you want to deal with collision and there is any. |

The last two files can be deleted once the signature file is generated.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/core/flirt/how-tos/generate-flirt-signatures-from-libraries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.