Wwise SDK 2022.1.17
|
The premake
command generates the solutions that will be used by the build
command to build your plug-in. The default Premake configuration file generated by the new
command works out of the box, however, further modifications will be needed to work on your plug-in. The generated solutions should not be modified directly as calling the premake
command again will overwrite all changes to these files. Instead, modify the Premake configuration file. This configuration file is located at the root of your plug-in and is named PremakePlugin.lua.
Looking at the top of the PremakePlugin.lua file, notice a global table named Plugin is created. It contains the definition of the Wwise plug-in that Premake will import and use to generate the required projects and solutions. Entries of that table include the following:
SignTool.exe
in a post-build step to sign dynamic libraries on Windows. When the array is empty, the post-build step is not added to the project.Notice how the rest of the file is divided into three similar sections. Each section contains a table with various lists of strings that are used to configure how a solution is generated:
Further information on how to populate each list is found in the Premake documentation:
Once the plug-in project has been created, other commands, such as premake
, must be called from within the project folder. Here is how to generate the solutions for Authoring on the current operating system:
Available platforms are:
Android, Authoring, Authoring_Windows, Authoring_Linux, Authoring_Mac, WinGC, XboxOneGC, iOS, Linux, LinuxAuto, Mac, NX, OpenHarmony, PS4, PS5, QNX, tvOS, visionOS, UWP_vc140, UWP_vc150, UWP_vc160, UWP_vc170, Windows_vc140, Windows_vc150, Windows_vc160, Windows_vc170, XboxOne, XboxSeriesX
When the solutions are generated, refer to Building Your Project for the Different Wwise Platforms to build and install your plug-in in your Wwise installation.
Note: To disable the code signing post-build step of shared libraries during development, you may pass the flag –disable-codesign to the premake action. |
Even though it is not included in the generated PremakePlugin.lua
file, there is also an optional Plugin.sdk.authoringstatic
table. This is used for unique use cases and provides a different configuration for the static SDK plug-in that is linked to the Authoring plug-in. For example, this demonstrates how to re-use the same SDK plug-in code with a FOR_AUTHORING
compiler define:
Notice how configuring a project is fairly straightforward since most of the Premake code is hidden in the configuration table. For a more advanced configuration, add a custom
field to any of the following configuration sections:
Next section: Building Your Project for the Different Wwise Platforms
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise