This section describes how to build and clean WebAssembly modules in a Web application.
Building WebAssembly-Enabled Web Applications
Although WebAssembly modules are automatically built whenever you build or launch their parent Web application project, they can also be built individually, if required.
When building WebAssembly modules from a parent Web application project, active build configurations currently set in the modules are used for their build.
To set the active build configuration for a module, right-click the WebAssembly module project and select "Build Configurations > Set Active", and then either "Debug" or "Release".
Figure 1. Set the Active Build Configuration
Note A Web application project package contains WebAssembly modules built using the currently set build configuration ("Debug" or "Release"). Compared to the "Release" configuration, the "Debug" configuration generally produces artifacts optimized for debugging as opposed to runtime speed or size.
A Web application project package contains WebAssembly modules built using the currently set build configuration ("Debug" or "Release"). Compared to the "Release" configuration, the "Debug" configuration generally produces artifacts optimized for debugging as opposed to runtime speed or size.
To build a WebAssembly module, right-click the module project and select "Build Project".
Figure 2. Build a WebAssembly Module
Note If nothing happens when you try to build a module, it can mean that neither the project content, nor its build configuration has changed since the last successful build and the built artifacts are current. If you want to force the build anyway, clean the project. This makes the build tool available again.
If nothing happens when you try to build a module, it can mean that neither the project content, nor its build configuration has changed since the last successful build and the built artifacts are current. If you want to force the build anyway, clean the project. This makes the build tool available again.
The build progress can be observed in the "Console" tab. If the build console is not visible, open it by clicking the button as shown in the figure below and selecting either "CDT Build Console" or "CDT Global Build Console."
If there are errors or warnings during the build, they are visible in the build console and in the "Problems" tab. Double-clicking on a compilation error or warning moves you to the source code where the error occurred.
Figure 3. Build Console
When the build is finished, its artifacts can be found under the "CurrentBin" folder within the project's tree.
To build a WebAssembly module for all the available build configurations, right click the module project and select "Build Configurations > Build All".
The WebAssembly module is built with each of the available build configurations. By default, there are two available: "Debug" and "Release".
Build artifacts are to be found under folders named after the build configurations (by default, "Debug" and "Release").
The "CurrentBin" folder contains the build artifacts for the currently active build configuration. The content is the same as in the respective "Debug" or "Release" folder.
To clean a WebAssembly project for the active build configuration, right-click the module project and select "Clean Project".
To clean a WebAssembly project for all available build configurations, right-click the module project and select "Build Configurations > Clean All".