Hey folks, Might be a silly question so excuse me if I’m a bit too new to this, but where can I fin...

# compose-desktop

[Marin Tolić]

Hey folks,

Might be a silly question so excuse me if I’m a bit too new to this, but where can I find the option to create an installer?

Ive gone through this tutorial: https://github.com/JetBrains/compose-jb/tree/master/tutorials/Native_distributions_and_local_execution

Unfortunately I cannot say I fully understand the matter and how to trigger building an installer.

Any help would be greatly appreciated and sorry for the bother 🙂

[xetra11]

Installer for what exactly?

[xetra11]

when running gradle packageMsi you build your app to the MSI (windows installer) myapp.msi file

[xetra11]

when running gradle packageDeb you create a debian package which can be installed by some linux apps like "eddy" so almost an installer

[Marin Tolić]

In this case a .dmg on my mac and later on a debian for my linux distro

[xetra11]

Ah ok - for those I can't help. I am currently working on a way to distribute the .deb file to dpkg to have it avaialble there as an "installer"

[Marin Tolić]

Right, but you did successfully manage to generate a .deb file right?

[Marin Tolić]

Think you’ve pointed me in the right direction with the packaging, I just need to better understand how to configure it.

I’m used to Android where things are pretty much pre set for us

[xetra11]

Right, but you did successfully manage to generate a .deb file right?

Yes

[xetra11]

I don't think you need much configuration for it as far as I know

[xetra11]

https://github.com/xetra11/CK3-Workbench/blob/22eafbbdfa1d289af063599bec84e016aa095a9e/build.gradle.kts#L67

[Marin Tolić]

Could you show me the specific part of the Gradle script designed to go thruogh the process, because I thought this would be covered by targetFormats, however it seems that I may be wrong

[xetra11]

take a look here - that's all I did

[Marin Tolić]

Beat me to the punch, thank you very much!

[Marin Tolić]

Yup, there doesn’t seem to be much that’s diffferent here.

Did your .deb file get build with running the app or did you have to go through a special process akin to what we have in ANdroid with building the APK or signed bundles

[xetra11]

Uff no idea what you Android peoples are doing 😛 I never used it.
My process really simply is gradle packageDeb - all things build steps are included in there as far as I understand

[xetra11]

and in the build/compose/... folder then I find the .deb file

[xetra11]

Run ./gradlew packageDeb
  ./gradlew packageDeb
  shell: /bin/bash -e {0}
  env:
    JAVA_HOME_15.0.1_x64: /opt/hostedtoolcache/jdk/15.0.1/x64
    JAVA_HOME: /opt/hostedtoolcache/jdk/15.0.1/x64
    JAVA_HOME_15_0_1_X64: /opt/hostedtoolcache/jdk/15.0.1/x64
Downloading <https://services.gradle.org/distributions/gradle-6.5.1-bin.zip>
.........10%..........20%..........30%..........40%.........50%..........60%..........70%..........80%.........90%..........100%

Welcome to Gradle 6.5.1!

Here are the highlights of this release:
 - Experimental file-system watching
 - Improved version ordering
 - New samples

For more details see <https://docs.gradle.org/6.5.1/release-notes.html>

Starting a Gradle Daemon (subsequent builds will be faster)
> Task :compileKotlin
w: /home/runner/work/CK3-Workbench/CK3-Workbench/src/main/kotlin/com/github/xetra11/ck3workbench/app/AppShutdownService.kt: (27, 11): Elvis operator (?:) always returns the left operand of non-nullable type Unit
w: /home/runner/work/CK3-Workbench/CK3-Workbench/src/main/kotlin/com/github/xetra11/ck3workbench/app/view/ProjectCreateView.kt: (66, 17): Variable 'newProject' is never used

> Task :compileJava NO-SOURCE
> Task :processResources
> Task :classes
> Task :inspectClassesForKotlinIC
> Task :jar
WARNING: Using incubator modules: jdk.incubator.jpackage

> Task :packageDeb
The distribution is written to /home/runner/work/CK3-Workbench/CK3-Workbench/build/compose/binaries/main/deb/ck3-workbench_0.0.50-1_amd64.deb

BUILD SUCCESSFUL in 2m 1s
5 actionable tasks: 5 executed

[Marin Tolić]

I was missing that step with running a separate gradle process, I though it was all done through automatization.

Thank you very much @xetra11, you’ve helped me a great deal!

[xetra11]

no problem - next time you help me out!