Get started with Apax and AX Projects

<h2>Learning path</h2>
<h1>SIMATIC AX</h1>
<h3>Get started with Apax and AX Projects</h3>
---
<div class="grid-slide-1x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Table of Contents</h2>
    </header>
  </div>
  <div class="kachel1">
    <p><strong>00 - Prerequisites</strong></p>
    <p>01 - Introduction to package management</p>
    <p>02 - Use Apax</p>
    <p>03 - Building the project</p>
    <p>04 - Summary</p>
    <p>05 - Feedback</p>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2> What will you learn in this chapter</h2>
    </header>
  </div>
  <div class="kachel1">
    <p>After you completed this training section you will </p>
        <ul>
            <li>understand the basics of package management</li>
            <li>know how to use apax to create and build a new project</li>
            <li>have learned about:</li>
            <ul>
                <li>the overall structure of an AX project </li>
                <li>project templates and dependencies</li>
                <li>the project manifest file</li>
                <li>how to build the project</li>
            </ul>
        </ul>
    <br>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Prerequisites</h2>
    </header>
  </div>
  <div class="kachel1">
    <ul>
      <li>to get started, you need to have SIMATIC AX, apax and all its prerequisites installed </li>
      <li>in addition, you should know the basics on how to use AX Code</li>
      <li>basic knowledge of using the command line interface (CLI) is also required. This includes:</li>
      <ul>
        <li>how to open a CLI</li>
        <li>how to change directories</li>
        <li>how to execute commands</li>
      </ul>
      <br/>
      <li>with this, you are set up to continue with this learning path</li>
    </ul>
  </div>
</div>
---
<div class="grid-slide-1x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>Overview</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>00 - Prerequisites</p>
    <p><strong>01 - Introduction to package management</strong></p>
    <p>02 - Use Apax</p>
    <p>03 - Building the project</p>
    <p>04 - Summary</p>
    <p>05 - Feedback</p>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
  <h2>Introduction to package management</h2>
  <h3>Overview</h3>
  </header>
  </div>
  <div class="kachel1">
  <p>In this chapter, you will learn about:</p>
  <ul>
    <li>what package management is and why it is important</li>
    <li>the role of apax in package management within Simatic AX</li>
    <li>key concepts such as dependencies, registries, and packages</li>
  </ul>
  </div>
  <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>What is Apax?</h3>
    </header>
  </div>
  <div class="kachel1">
    <li>Apax is the central tool within Simatic AX, acting as a package manager and a build tool</li>
    <li>Apax is a command line interface tool that serves as a package manager and facilitator for each step in the development workflow</li>
    <li>it helps you create, build, and manage AX projects efficiently</li>
    <div class="definition"><code>apax</code> automates the process of retrieving and managing project dependencies, making it easier to develop and maintain AX projects.</div>
    <br>
  </div>
  <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>What is a package manager?</h3>
    </header>
  </div>
  <div class="kachel1">
    <li>A package manager is a tool that automates the process of installing, updating, and managing software packages and their dependencies</li>
    <br>
    <li>it retrieves libraries and tools (packages) required for your project from central databases (registries) and downloads them to your PC</li>
    <div class="definition">
      a package manager simplifies the process of managing software dependencies and ensures that your project has all the necessary components to run correctly.
    </div>
    <p>common examples of package managers include npm for JavaScript, pip for Python, and apax for AX projects.</p>
  </div>
  <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>

---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>Configuration file for package manager</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Typically a package manager requires a configuration file named <code>apax.yml</code>. This file contains many entries that define:</p>
    <ul>
      <li>metadata</li>
      <li>target systems</li>
      <li>registries</li>
      <li>dependencies</li>
      <li>devDependencies</li>
      <li>custom scripts</li>
      <li>custom variables</li>
    </ul>
    <p>In the case of <strong>Apax</strong> the name of the configuration file is <code>apax.yml</code></p>
  </div>
  <div class="kachel2">
    <img src="img/apax_yml.svg" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>
---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>What is a package?</h3>
    </header>
  </div>
  <div class="kachel1">
  <p>A package is a bundle of code that provides specific functionality and can be easily shared and reused. It typically includes tools, compiled code, or source code. Examples of packages are:</p>
  <ul>
    <li>tools like the ST compiler (STC) or SIMATIC loader (SLD)</li>
    <li>system libraries like IEC Timer or Motion Control</li>
    <li>user libraries that come from GitHub or are self-created</li>
  </ul>
  <p>Packages can be individually updated, which significantly simplifies the process of updating a library.</p>
  <p>The full package name then becomes something like <code>@ax/package-name</code>, helping in organizing and managing packages, especially when dealing with multiple registries.</p>
  </div>
  <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>
---
<div class="grid-slide-1x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Introduction to package management</h2>
      <h3>Understanding package versions</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Packages in Apax use semantic versioning (semver): <code>MAJOR.MINOR.PATCH</code>.</p>
    <ul>
      <li><strong>MAJOR:</strong> incompatible changes (e.g., <code>1.0.0</code> to <code>2.0.0</code>)</li>
      <li><strong>MINOR:</strong> new features, backward-compatible (e.g., <code>1.0.0</code> to <code>1.1.0</code>)</li>
      <li><strong>PATCH:</strong> bug fixes, backward-compatible (e.g., <code>1.0.0</code> to <code>1.0.1</code>)</li>
    </ul>
    <p>Examples:</p>
    <ul>
      <li><code>@ax/system-timer@1.0.0</code> to <code>@ax/system-timer@2.0.0</code>: major update</li>
      <li><code>@ax/system-timer@1.0.0</code> to <code>@ax/system-timer@1.1.0</code>: minor update</li>
      <li><code>@ax/system-timer@1.0.0</code> to <code>@ax/system-timer@1.0.1</code>: patch update</li>
    <p>The caret symbol <code>^</code> in version (e.g., <code>^1.0.0</code>) allows updates that do not change the first non-zero digit (e.g., <code>1.x.x</code>). Example <code>apax.yml</code> configuration:
    <pre><code>
    dependencies:
      "@ax/system-timer": ^1.0.0
    </code></pre>
    </p>
</div>
---

<div class="grid-slide-2x1-container">
    <div class="grid-slide-header">
    <header class="slide_header">
        <h2>Introduction to package management</h2>
        <h3>Understanding dependencies</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Dependencies are external libraries or tools that your project needs to function correctly.</p>
    <br>
    <p>There are two types of dependencies:</p>
    <ul>
        <li><strong>dependencies:</strong> required for the project to run</li>
        <li><strong>devDependencies:</strong> required for development and testing but not for running the project</li>
    </ul>
    <div class="definition">dependencies are like ingredients in a recipe, while devDependencies are like the tools used to prepare the recipe.</div>
  </div>
  <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Introduction to package management</h2>
    <h3>Differences between dependencies and devDependencies</h3>
  </header>
  </div>
  <div class="kachel1">
  <ul>
    <li><strong>Dependencies:</strong> these are essential for the project to run. They are like the ingredients in a recipe that you need to make the final dish. For example, a system-timer library is a dependency because it is required for the application to function</li>
    <li><strong>devDependencies:</strong> these are only needed during the development and testing phases but not for running the project. They are like the tools used to prepare the recipe, such as a mixer. For example, an SDK (Software Development Kit) is a devDependency because it is used to build and test the project but is not needed in the final application</li>
  </ul>
  </div>
    <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Introduction to package management</h3>
    <h3>What is a registry?</h3>
  </header>
  </div>
  <div class="kachel1">
  <ul>
    <li>A registry is a central database where packages are stored and maintained. It acts as a repository from which package managers can retrieve the necessary packages. Registries can be public or private, and they help in managing and distributing packages efficiently</li>
    <li>for SIMATIC AX, the default registry does not need to be specified</li>
    <li>if you want to fetch packages from other registries like GitHub or NPM, you need to configure apax to recognize these registries</li>
    <li>a scope is a way to group related packages together, usually defined by a prefix, such as <code>@ax</code> for SIMATIC AX packages</li>
  </ul>
  </div>
    <div class="kachel2">
    <img src="img/apax_registries.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>

---
<div class="grid-slide-1x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Use Apax</h2>
      <h3>Overview</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>00 - Prerequisites</p>
    <p>01 - Introduction to package management</p>
    <p><strong>02 - Use Apax</strong></p>
    <p>03 - Building the project</p>
    <p>04 - Summary</p>
    <p>05 - Feedback</p>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Use Apax</h2>
    <h3>Overview</h3>
  </header>
  </div>
  <div class="kachel1">
  <p>In this section, you will learn about:</p>
  <ul>
    <li>verify Apax installation: <code>apax --version</code></li>
    <li>create projects with templates: <code>apax create [template] [project-name]</code></li>
    <li>important templates: <strong>app</strong>, <strong>lib</strong>, <strong>empty</strong>, <strong>quickstart</strong>, <strong>workspace</strong>, <strong>template</strong></li>
    <li>project structure: <strong>apax.yml</strong>, <strong>src/</strong>, <strong>test/</strong></li>
    <li>install dependencies: <code>apax install</code></li>
  </ul>
  </div>
    <div class="kachel2">
    <img src="img/apax_overview.svg" alt="Bild 2" style="width: 100%;">
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Use Apax</h2>
    <h3>First use of Apax</h3>
  </header>
  </div>
  <text class="kachel1">
  <p>To verify that Apax is installed correctly and to check its version, you can use the following command in your terminal:</p>
  <pre><code>apax --version</code></pre>
  <br>
  <p>this command will display the current version of Apax installed on your system.</p>
  </text>
    <div class="kachel2">
    <img src="img/apax_version.gif" alt="Bild 2" style="width: 100%;">
  </div>
  </div>

</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Logging into a registry</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Before you can fetch packages from a registry, you need to log in. This is done using the <code>apax login</code> command. Since we are not using any external registries at this point, we will log in to the <code>@ax</code> registry.</p>
    <pre><code>apax login</code></pre>
    <p>This command will login for the <code>@ax</code> registry. Once logged in, you will be able to fetch and manage packages from this registry.</p>
  </div>
    <div class="kachel2">
    <img src="img/apax_login.gif" alt="Bild 2" style="width: 100%;">
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - project templates</h3>
    </header>
  </div>
  <div class="kachel1">
    <ul>
      <li>with Apax, projects can be created based on so-called project templates</li>
      <li>each project template is essentially a package that is downloaded and unpacked as a new project using the command <code>apax create</code></li>
      <li>the advantage is that there are not only fixed project templates; every user can create their own project templates and store them in a registry to make them available</li>
    </ul>
  </div>
  <div class="kachel2">
    <img src="img/create_project.gif" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - important project templates</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>There are two main templates you can use with <code>apax create</code>:</p>
    <ul>
      <li><strong>app:</strong> this template is used to create an application project. An application project is designed to run on a real runtime environment, such as an S7-1500 PLC</li>
      <li><strong>lib:</strong> this template is used to create a library project. A library project is intended to be published as a package and can be reused in applications or other libraries</li>
    </ul>
  </div>
  <div class="kachel2">
    <img src="img/create_project.gif" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - further templates</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>In addition to the <strong>app</strong> and <strong>lib</strong> templates, Apax offers several other templates to help you get started with different types of projects:</p>
    <ul>
      <li><strong>empty</strong> a generic template for creating a minimal project setup</li>
      <li><strong>quickstart</strong> a template designed to help you quickly get started with Simatic AX</li>
      <li><strong>workspace</strong> a template for setting up a workspace with multiple projects</li>
      <li><strong>template</strong> a template for custom template that can be created and used based on specific user requirements</li>
    </ul>
    <p>These templates can be used to streamline the project creation process and ensure that you have the necessary structure and dependencies in place from the start.</p>
  </div>
  <div class="kachel2">
    <img src="img/create_project.gif" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - Apax create</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>The <code>apax create</code> command allows you to create a new project from a template. The syntax for this command is:</p>
    <pre><code>apax create [template] [project-name]</code></pre>
    <p>Here, <code>[template]</code> is the name of the template you want to use, and <code>[project-name]</code> is the name of the new project. There are several templates available, but the most important ones are <strong>app</strong> and <strong>lib</strong>.</p>
    <p>For example, to create a new application project named "my-first-app", you would use the following command:</p>
    <pre><code>apax create app my-first-app</code></pre>
  </div>
    <div class="grid-slide-ressources">
    <ol>
      <li>apax create CLI reference: <br><a href="https://console.simatic-ax.siemens.io/docs/apax/cli#create">https://console.simatic-ax.siemens.io/docs/apax/cli#create</a></li>
    </ol>
</div>
  <div class="kachel2">
    <img src="img/create_project.gif" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - generated project structure</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>After creating the project and opening it in AxCode, you will see the following structure:</p>
    <ul>
      <li><strong>apax.yml:</strong> the project manifest file, which we will explore in the next slide</li>
      <li><strong>src/:</strong> contains all the source code for your project, including a <code>configuration.st</code> and a <code>program.st</code>, both written in Structured Text, a standardized language for automation systems. These files will be covered in detail in the chapter on ST Programming</li>
      <li><strong>test/:</strong> contains unit tests for your project</li>
    </ul>
    <p>This structure helps in organizing your project files and dependencies efficiently.</p>
  </div>
  <div class="kachel2">
    <img src="img/ax_project_structure.png" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Using Apax</h2>
    <h3>Creating a project - the apax.yml</h3>
  </header>
  </div>
  <div class="kachel1">
  <p>When you open the project with AX Code, you will find an <code>apax.yml</code> file. This file is the project manifest and contains important information about the project, such as:</p>
  <ul>
    <li><strong>name:</strong> the name of the project</li>
    <li><strong>version:</strong> the version of the project</li>
    <li><strong>type:</strong> the type of the project (app, lib)</li>
    <li><strong>devDependencies:</strong> the libraries and tools required for development and testing</li>
  </ul>
  <p>This file helps in defining everything specific to the project, automating workflows with scripts, and specifying where the code is supposed to run.</p>
  </div>
  <div class="grid-slide-ressources">
    <ol>
      <li>apax.yml manifest reference: <br><a href="https://console.simatic-ax.siemens.io/docs/apax/yml">https://console.simatic-ax.siemens.io/docs/apax/yml</a></li>
    </ol>
</div>
  <div class="kachel2">
    <img src="img/apaxyml.png" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
      <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - understanding type app and lib</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Let's take a closer look at the <strong>app</strong> and <strong>lib</strong> types:</p>
    <ul>
      <li><strong>app:</strong>
        <ul>
          <li>a PLC application that can be loaded onto an S7-1500</li>
          <li>example: software for machine control</li>
        </ul>
      </li>
      <li><strong>lib:</strong>
        <ul>
          <li>a library from which a package can be built</li>
          <li>can be reused in other libraries or applications</li>
        </ul>
      </li>
    </ul>
  </div>
  <div class="kachel2">
    <img src="img/apaxyml.png" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - understanding the field: devDependencies</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>The <code>devDependencies</code> field in the <code>apax.yml</code> file lists the tools and libraries required for developing and testing your project. By default, it includes the latest SDK (Software Development Kit).</p>
    <ul>
      <li>an SDK is a collection of tools necessary for developing, loading, and debugging PLC software</li>
      <li>for example, it includes the ST Compiler and the SIMATIC Loader</li>
      <li>one of the advantages of using package management is the ability to switch to a newer or older SDK version without needing to migrate the project</li>
      <li>this flexibility ensures that you can always use the most suitable tools for your development needs</li>
    </ul>
  </div>
  <div class="kachel2">
    <img src="img/apaxyml.png" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Creating a project - understanding the field: targets</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>The <code>targets</code> field in the <code>apax.yml</code> file specifies the target platforms for your project. Currently, the possible values are <strong>1500</strong> and <strong>LLVM</strong>.</p>
    <ul>
      <li><strong>1500:</strong> this target is used for S7-1500 PLCs</li>
      <li><strong>LLVM:</strong> this target is used for the AxUnit Testing Framework</li>
    </ul>
    <p>By defining the target, you ensure that the project is compiled and built for the correct platform, whether it's for deployment on a PLC or for running unit tests.</p>
  </div>
  <div class="kachel2">
    <img src="img/apaxyml.png" alt="Bild 1" style="width: 100%;">
  </div>
  </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Installing dependencies</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Before starting your project, install the dependencies with:</p>
    <pre><code>apax install</code></pre>
    <br>
    <ul>
      <li>this command downloads all dependencies and devDependencies listed in the apax.yml file to the .apax folder</li>
      <li>it creates an apax-lock.json file with the installed packages and their versions</li>
      <li>this ensures your project has all necessary components and correct dependency versions</li>
    </ul>
  </div>
      <div class="grid-slide-ressources">
    <ol>
      <li>apax package management: <a href="https://console.simatic-ax.siemens.io/docs/apax/yml#package-management">https://console.simatic-ax.siemens.io/docs/apax/yml#package-management</a></li>
    </ol>
  </div>
  <div class="kachel2">
    <img src="img/apax_install.gif" alt="Bild 1" style="width: 100%;">
  </div>
  </div>

---

<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Using Apax</h2>
      <h3>Adding dependencies</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>To add a new dependency to your project, you can use the <code>apax add</code> command. For example, to add the <code>@ax/system-timer</code> package, you would use the following command:</p>
    <pre><code>apax add @ax/system-timer</code></pre>
    <p>When you run this command, the following happens:</p>
    <ul>
      <li>the <code>@ax/system-timer</code> package is fetched from the registry</li>
      <li>the <code>apax.yml</code> has a new entry <code>dependencies:</code></li>
      <pre><code>dependencies:
      "@ax/system-timer": ^8.0.8</code></pre>
      <li>the <code>apax-lock.json</code> file is updated to lock the version of the added package</li>
    </ul>
  </div>
  <div class="kachel2">
    <img src="img/apax_add.gif" alt="Bild 1" style="width: 100%;">
  </div>
</div>

<!-- ---

<div class="grid-slide-2x1-container">
    <div class="grid-slide-header">
    <header class="slide_header">
        <h2>Building the project</h2>
        <h3>Installing dependencies</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>To download these packages you have to execute the following command:</p>
    <pre><code>apax install</code></pre>
    <br>
    <p>This will collect all dependencies and devDependencies of the apax.yml and download them to the .apax folder.</p>
    <p>Additionally it will create an apax-lock.json file. This file will contain all packages that have been installed, when you check it you will see, that the SDK has a lot of sub-dependencies that it brings along.</p>
  </div>
  <div class="kachel2">
    <pre><code data-line-numbers data-trim data-noescape>
    "packages": {
      "@ax/hwc": {
        "name": "@ax/hwc",
        "version": "1.0.225",
        "integrity": "sha512-fesFsmJoCz3...",
        "dependencies": {
          "@ax/hwc-win-x64": "1.0.225",
          "@ax/hwc-linux-x64": "1.0.225"
        }
      },
      "@ax/hwld": {
        "name": "@ax/hwld",
        "version": "1.0.75",
        ...
      }
    </code><pre>
  </div>
  <div class="grid-slide-ressources">
    <ol>
     <li>apax install CLI reference: <br><a href="https://console.simatic-ax.siemens.io/docs/apax/cli#install">https://console.simatic-ax.siemens.io/docs/apax/cli#install</a></li>
      <li>package-locks: <br><a href="https://docs.npmjs.com/cli/v6/configuring-npm/package-locks">https://docs.npmjs.com/cli/v6/configuring-npm/package-locks</a></li>
    </ol>
  </div>
</div> -->
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Building the project</h2>
      <h3>Overview</h3>
    </header>
    </div>
    <div class="kachel1">
    <p>00 - Prerequisites</p>
    <p>01 - Introduction to package management</p>
    <p>02 - Use Apax</p>
    <p><strong>03 - Building the project</strong></p>
    <p>04 - Summary</p>
    <p>05 - Feedback</p>
    </div>
</div>
---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
  <header class="slide_header">
    <h2>Building the project</h2>
    <h3>Overview</h3>
  </header>
  </div>
  <div class="kachel1">
  <p>In this section, you will learn about:</p>
  <ul>
    <li>how to build the project using Apax: <code>apax build</code></li>
    <li>the role of the Structured Text compiler (stc) in the build process</li>
    <li>where to find the generated binaries</li>
  </ul>
  </div>
  <div class="kachel2">
    <img src="img/apaxbuild.gif" alt="Bild 1" style="width: 100%;">
  </div>
</div>
---
<div class="grid-slide-2x1-container">
    <div class="grid-slide-header">
    <header class="slide_header">
        <h2>Building the project</h2>
        <h3>Compiling the source code</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Now that all packages have been installed, we can build the project using this command:</p>
    <pre><code>apax build</code></pre>
    <br>
    <p>This will invoke the <code>stc</code> (Structured Text compiler) and transform the source code into a target specific binary. This binary can then be loaded onto the PLC.</p>
    <br>
    <p>The compiler will check for any syntactical or semantical errors and abort the compilation if the code has errors.</p>
  </div>
  <div class="kachel2">
    <pre><code data-trim data-noescape data-line-numbers>
    > apax build  
   ✔ Package verification succeeded.
    using targets 
    stc --input C:\MyProject\src 
        --target s7generic --output bin\1500 
        --compile-to app:myapp:0.1.0 --debug
    AX Structured Text (ST) compiler V7.0.52.28545.
    info: stc[0]
    Compile finished with 0 error(s).
    </code><pre>
  </div>
  <div class="grid-slide-ressources">
    <ol>
      <li>stc CLI reference: <br><a href="https://console.simatic-ax.siemens.io/docs/st/cli#stc-command-line-reference">https://console.simatic-ax.siemens.io/docs/st/cli#stc-command-line-reference</a></li>
    </ol>
  </div>
</div>

---

<div class="grid-slide-2x1-container">
    <div class="grid-slide-header">
    <header class="slide_header">
        <h2>Building the project</h2>
        <h3>Compiling the source code</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>Now that you have compiled, you will be able to find the binary file in the respective target subfolder in the bin directory. You can define the target in the apax.yml manifest.</p>
    <br>
    <div class="warning">
      ><strong>Note:</strong> You have to recompile every time you want to download changes, otherwise the old binary will be loaded.
    </div>
  </div>
  <div class="kachel2">
    <pre><code data-line-numbers = "5" data-trim data-noescape>
    > apax build  
   ✔ Package verification succeeded.
    using targets 
    stc --input C:\MyProject\src 
        --target s7generic --output bin\1500 
        --compile-to app:myapp:0.1.0 --debug
    AX Structured Text (ST) compiler V7.0.52.28545.
    info: stc[0]
    Compile finished with 0 error(s).
    </code><pre>
  </div>
</div>

---
<div class="grid-slide-2x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>Getting Started</h2>
      <h3>Complete Workflow</h3>
    </header>
  </div>
  <div class="kachel1">
    <p>For a detailed guide on the complete workflow from creating a project to downloading it onto a PLC, refer to the <strong>Getting Started</strong> guide.</p>
    <p>In the <strong>Getting Started</strong> guide, you will learn about:</p>
    <ul>
      <li>creating a new project using Apax templates</li>
      <li>installing dependencies with <code>apax install</code></li>
      <li>building the project using <code>apax build</code></li>
      <li>downloading the compiled binary to a PLC</li>
      <li>monitor and debug the application</li>
    </ul>
  </div>
  <div class="grid-slide-ressources">
    <ol>
      <li>Getting Started: <br><a href="https://console.simatic-ax.siemens.io/docs/get-started/guides_overview">https://console.simatic-ax.siemens.io/docs/get-started/guides_overview</a></li>
    </ol>
  </div>
</div>
---
<div class="grid-slide-1x1-container">
  <div class="grid-slide-header">
    <header class="slide_header">
      <h2>What did you learn</h2>
    </header>
  </div>
  <div class="kachel1">
    <p>In this section you learned about...</p>
    <ul>
      <li>what apax is</li>
      <li>basics of package management</li>
      <li>how to create a project from a template and its basic structure</li>
      <li>how to build the project</li>
    </ul>
    <br>
    <p>you can now create your own project and continue with the next section</p>
  </div>   
</div>
---

<h2>Thanks for using the</h2>
<h1>SIMATIC AX</h1>
<h2>learning path</h2>
<h4><a href="https://github.com/simatic-ax/introduction_apax/issues/new/choose">I want to give feedback</a></h4>
<br>
<h4><a href="https://github.com/simatic-ax/axlp_apax_and_project_creation">I want to contribute</a></h4>