Building a Binary Extension

Once you've created a scripted extension, you can turn it into a compiled binary extension to be shared with ANSYS users. A separate compiler is not necessary. ACT provides its own process for encapsulating the scripted extension to a binary format that users cannot view or edit.

The encapsulation of the scripted extension generates a WBEX file. When you build a binary extension, the resulting WBEX file contains all files or directories necessary for the extension.

Accessing the Binary Extension Builder

You can use any of the following methods to access the binary extension builder:

The appearance of the binary extension builder depends on how it was accessed.

Building a Binary Extension

To build a binary extension, do the following:

  1. If the builder was accessed from the Extensions menu, for Scripted Extension to Build, select the extension to build as a WBEX file.

    Choices include all scripted extensions in directories defined in the Extension tab of the Options dialog box. For more information, see Configuring Extension Options. Both the extension name and version are shown to avoid confusion if multiple versions of an extension are defined.

     

    If the builder was accessed from the Extension Manager or ACT App Builder, the Scripted Extension to Build option is not shown because an extension selection has already been made.

  2. Identify the folder in which to output the WBEX file.

  3. Specify a security level for sharing the extension.

    Your selection specifies whether the extension can be saved within an ANSYS Workbench project and, when that project is shared, if the extension can be loaded with the shared project. The security level allows the developer of the extension to control how the extension can be shared and used with various projects. Choices are:

    • Can copy extension to project: Each time a user asks to save the extension with a project, the extension itself is copied into the project and consequently is available each time the project is opened. The extension can also be used with other projects.

    • Can copy extension to project but locked to this one: The extension can be saved within a project, as with the previous option, but the use of the extension is limited to the current project. If a user opens a new project, the extension is not available.

    • Can't copy extension to project: The extension is not saved with the project and is not shared with other users of the project.


    Note:
    • The extension can be sent separate from a project. The process for saving extensions within a project is described in Configuring Extensions to be Loaded by Default.

    • Security options only apply if the user wants to save the extension with the project. Otherwise, they are not applicable.


    Once all options are specified, the Build button is enabled.

  4. Click Build to launch the build.

While the build is in progress, the bottom part of the window displays build information. Script Processing describes how references to multiple IronPython scripts in an XML extension definition file are processed.


Release 18.2 - © ANSYS, Inc. All rights reserved.