Open justme-1968 opened 5 months ago
Plugin packaging is definitely still a manual process, I have a similar shell script I use for automatically building and packaging my plugins. It might be worth expanding on how to package a plugin in the README.
i just found your repository yesterday and had a quick qo on a plugin for my home automation project. i really like writing a stremdeck plugin in swift, but after the first trials i got very annoyed with the manual packaging of the resulting plugin.
i first thought of using a package plugin for a post build step, but this is currently not possible. only pre build and build plugins currently.
then i just had a very quick and dirty go at a post-build step for the build scheme. unfortunately this seems to be also quite limited for packages, but with some brute force i got it to work.
maybe this is also useful for others...
prerequisites:
Tools
directory on the same level as the plugin'sSources
with the DistributionTool binary and the following createPlugin.sh script which should be executableResources
directory, also on the same level asSources
, with everything else required for the finished plugin likeIcons/...
,previews/...
and language json filesthen add the script to a post-build phases of the relevant build schemes.
all this can be under source control
the script will create a
plugin
directory, assemble all the parts for the finished plugin and then call DistributionTool to create the packaged plugin there. and opens a finder window. you can just double click the.streamDeckPlugin
file as usual to install the plugin into the streamdeck software. a log file for the process is created in /tmp/you probably want to exclude
plugin
from source control. or change the script to create it somewhere else. the $URI should also adjusted to match the api specs and your prefix.createPlugin.sh: