It's been a while since I last posted an update about the Pinpit Gradle Plugin. A few days ago, I published version 0.7.0 to the Gradle plugin portal. Pinpit now supports packaging distributable zip archives for macOS 🎉. That completes the ability to build packages/installers cross-platform for all operating systems from a plain Ubuntu box. 🚀 That means you can build packages for all three major operating systems from your Linux development machine or CI server. If you're working on a different OS, building using a docker image should also work easily (we're testing building on CI machines, including the Github CI, but also tried vagrant and virtualbox based machines). I noticed that it takes quite a lot of work to set up all the assets required for a new project, such as the Gradle build script with everything configured and especially also the various launcher images and image assets for the Windows installer. To help with that, I created a command line tool that can do two things at the moment: 1. Create a new Compose for Desktop or Swing project from a template that builds using Gradle and the Pinpit plugin. After creating the app, it can directly be run using

./gradlew pinpitRun

or packaged using

./gradlew pinpitPackageDefault

. It also creates various assets from a Material symbol SVG file as input. That includes launcher files for Linux in PNG format, Windows in ICO format and macOS in ICNS format. 2. Update all the image assets in an existing project. If you decide to change your app icon, you can update all the relevant assets in a single step. At the moment any Material symbol can be used as input (just select the desired symbol, download as SVG and specify on the CLI). It should also be possible to support a custom logo SVG at a later step as the toolchain is already processing SVG, but at the moment it has some logic hardwired to work with Material symbols. For example, if you use the rocket launch icon and colors '0x127f73' for background and 'white' as foreground, you will get an launcher image as attached. Specify yet another color for the left side of the Windows installer background image (yellow in this case). The images are all generated as SVG too, so that you can start customizing your assets and use those images just as a starting point.

Are there plans to upstream features to compose-multiplatform plugin?

I'd love the compose-multiplatform plugin to develop in this direction, but it's not for me to say if that's a desired direction the upstream project is willing to take.

Hello, Sebastian! Trying to adopt Pinpit to my project. Could you help me with advice? Can I create several tasks for generating distributions in one project? If yes then how to configure each task without applying Pinpit plugin?

I'm not sure I understand. It is possible to configure for a project which targets to build, i.e. deb, msi, macos zip etc. by adding the relevant blocks in the Gradle build file. In contrast to the Compose plugin, it is not necessary or possible to specify a list of target formats. That's implicit by the blocks you add such as this for macOS:

macOS {
                packageName = "PinpitComposeHelloWorld"
                bundleID = "de.mobanisto.hello.world"
                appCategory = "public.app-category.utilities"
                distributableArchive {
                    format = "zip"
                    arch = "arm64"
                }
            }

For example, i want to create two .deb distributions for one projects. As i understand if using plugin it is possible to create only one per platform.

ah, good point. Indeed you can have multiple

deb()

blocks and build multiple debian packages for different distros. See briar for an example: https://github.com/briar/briar-desktop/blob/main/briar-desktop/build.gradle.kts#L223

Thanks, Sebastian!

From your last example I can see that configurations needed for distributions but I can't see where they are assigned to each variant.

you have a configuration such as

val macosArm64: Configuration by configurations.creating {
    extendsFrom(configurations.implementation.get())
}

and the plugin determines itself that this is the configuration to use for this target:

macOS {
                ...
                distributableArchive {
                    format = "zip"
                    arch = "arm64"
                }
            }

is that what you mean?

I understand that configuration is choosing for variant by some name convention depending of os and arch. But it will be good if there will be possibility to explicitly specify configuration for each variant. For example if I have two Deb variants for the same arch and for each i need different Gradle configuration.

OK, interesting. I created an issue to track this feature request: https://github.com/mobanisto/pinpit-gradle-plugin/issues/32 What's your use-case with this? What kind of dependencies do you need declared for different Debian-based distros?

I have custom gradle plugin that generates for one project several output for each platform. Ui thin client, service. I want for each output to make installer.

and that plugin creates some dependency configurations itself, i.e. if you could specify those on the pinpit tasks, things should probably work for your case?

Yes. I can make configuration for each plugin output by including output file to it. And if i could for each Pinpit distribution specify appropriate configuration it will solve my case.

another solution probably would be to have separate gradle modules for

ui

and

service

and let both apply the pinpit plugin. But maybe that doesn't fit the rest of your setup

I'm trying to avoid this. Want to make it in one project. So that i can apply plugin to it and get all needed distributions in its output

just out of curiosity: is this currently possible with the Compose plugin, did you find a way to make your thing work with that?

For Compose plugin for now in common target I write

compileOnly(project.ComposeDeps.runtime)

And in needed ui targtets i specify all needed Compose dependencies. There is request to make it truly separated but it hasn't done yet: https://github.com/JetBrains/compose-multiplatform/issues/537