Virtual method to be overridden by the user. It is called when the export starts and provides all information about the export. features is the list of features for the export, is_debug is true for debug builds, path is the target path for the exported project. flags is only used when running a runnable profile, e.g. when using native run on Android.
Virtual method to be overridden by the user. Called when the export is finished.
Virtual method to be overridden by the user. Called for each exported file, providing arguments that can be used to identify the file. path is the path of the file, type is the Resource represented by the file (e.g. PackedScene) and features is the list of features for the export. Calling skip inside this callback will make the file not included in the export.
Adds a custom file to be exported. path is the virtual path that can be used to load the file, file is the binary data of the file. If remap is true, file will not be exported, but instead remapped to the given path.
Adds an iOS bundle file from the given path to the exported project.
Adds a C++ code to the iOS export. The final code is created from the code appended by each active export plugin.
Adds a dynamic library (*.dylib, *.framework) to Linking Phase in iOS's Xcode project and embeds it into resulting binary. Note: For static libraries (*.a) works in same way as addIosFramework. This method should not be used for System libraries as they are already present on the device.
Adds a static library (*.a) or dynamic library (*.dylib, *.framework) to Linking Phase in iOS's Xcode project.
Adds linker flags for the iOS export.
Adds content for iOS Property List files.
Adds a static lib from the given path to the iOS project.
Adds a shared object with the given tags and destination path.
To be called inside _exportFile. Skips the current file, so it's not included in the export.
Construct a new instance of EditorExportPlugin. Note: use memnew!EditorExportPlugin instead.
A script that is executed when exporting the project.
Editor export plugins are automatically activated whenever the user exports the project. Their most common use is to determine what files are being included in the exported project. For each plugin, _exportBegin is called at the beginning of the export process and then _exportFile is called for each exported file.