Are we supposed to use proguard when packaging com...

# compose-desktop

[jQrgen]

Are we supposed to use proguard when packaging compose desktop .deb files?

I’m stuck with trying to fix warnings in proguard

Maybe just add `

-ignorewarnings

in proguard-rules.pro?

EDIT: I suspect that my proguard-pro file is not applied to JVM/Desktop. How is the proguard file connected to the desktop application? because using the -ignorewarnings in the proguard file is not working

[Alexander Maryanovsky]

You don’t have to, but typically you’d want to.

[jQrgen]

It’s not working. How do I disable proguard for desktop only?

[jQrgen]

Oh yay I found docs: https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-native-distribution.html#minification-and-obfuscation

[jQrgen]

ahhh: “For each default (without ProGuard) packaging task, the Gradle plugin provides a release task (with ProGuard):”

[jQrgen]

Can I just do ./gradlew packageDeb and host the deb on a website?

[Alexander Maryanovsky]

Sure

[Michael Paus]

You should configure ProGuard in your build.gradle.kts file.

Example:

compose.desktop {
    application {
        ...
        buildTypes.release {
            proguard {
                version.set("7.7")
                isEnabled.set(false)
                optimize.set(false)
                obfuscate.set(false)
                configurationFiles.from(project.file("<http://compose-desktop.pro|compose-desktop.pro>"))
            }
        }
    }
}

The above example effectively disables ProGuard.

[Alexander Maryanovsky]

But then, what’s the difference between that and the non-release tasks?

[Michael Paus]

You can always use the release tasks as usual but you can still switch on/off certain aspects of ProGuard depending on your needs.