> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalstartcompile2.md).

# OpalStartCompile2

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Preparation</td></tr><tr><td><strong>Description</strong></td><td><p>Starts the compilation steps, which separate the subsystems, generates the code and compiles each subsystem.<br><strong>This function enables you to specify:</strong></p><ul><li>options by subsystem</li><li><p>If numSubsys is equal to 0 and subsysName is equal to NULL, only the first option in the array will be read and this option will be applied to each subsystem.</p><p>option in the array will be read and this option will be applied to each subsystem</p></li></ul><p>Compilation continues after this function has returned with a return code of <strong>EOK</strong>. You must call <strong>OpalDisplayInformation</strong> to get the compilation results and the compilation termination status.</p><p>You may call <strong>OpalAbortCompile</strong> during the operation to stop the model's compilation. You must call <strong>OpalRegisterDisplay</strong> to register to receive status and compilation messages.</p></td></tr><tr><td><strong>Required Control</strong></td><td>System Control</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalStartCompile2</strong> (unsigned short numSubsys,char* subsysName[] unsigned int option[]);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>numSubsys:</strong> number of subsystems for which the compilation options arespecified. Should be equal to the number of calculation subsystem (console subsystem is not included).</li><li><strong>subsysName:</strong> array of the subsystem names.</li><li><strong>option:</strong> array of compilation options for each subsystem. Indicates which step of the compilation is to be completed. See <strong>OP_COMPILATION_DEFINE</strong>.</li></ul></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Command successfully issued (See Description for more information).</li><li><strong>OP_API_ESEPARATION:</strong> Error while separating the model's subsystems.</li><li><strong>OP_API_ECODE_GENERATION:</strong> Error while generating code for the subsystems.</li><li><strong>EPERM:</strong> System control was not granted to this client.</li><li><strong>EBUSY:</strong> Model executables already loaded.</li><li><strong>EBADF:</strong> Model not specified by previous OpalConnect or OpalSetCurrentModel.</li><li><strong>EIO:</strong> Error sending the request or receiving the reply.</li><li><strong>OP_API_ENO_PRODUCT:</strong> No license for RT-LAB and RT-LABx.</li><li><strong>OP_API_ENO_DEVELOP_LICENSE:</strong> No development license available.</li><li><strong>OP_API_ENO_TARGET_LICENSE:</strong> No license for selected target.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related items</strong></td><td>OpalAbortCompile, OpalDisplayInformation, OP_COMPILATION_DEFINE.</td></tr></tbody></table>


---

# 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://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalstartcompile2.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.
