Konstantin Kostov Gerry
10/21/2025, 12:45 PMpackageName per platform? I've been trying various combinations but it leads to strange results. For example, setting nativeDistributions.packageName and nativeDistributions.macOS.packageName results in nativeDistributions.packageName being used. If I also set nativeDistributions.windows.packageName the outcome is that the package name for windows is used for all platforms e.g.:
compose.desktop {
application {
mainClass = "org.example.project.MainKt"
nativeDistributions {
targetFormats(TargetFormat.Dmg, TargetFormat.Msi, TargetFormat.Deb)
packageName = "org.example.project"
packageVersion = "1.0.0"
macOS {
packageName = "Foo"
}
windows {
packageName = "Bar"
}
}
}
}ephemient
10/21/2025, 4:10 PMpackageName property across the whole nativeDistributions at configuration time, there isn't one for platform's settingsJacob Ras
10/21/2025, 4:19 PMKonstantin Kostov Gerry
10/22/2025, 7:07 AMnativeDistributions is organised, one has the impression that each platform offers an "override" to the global values when used. Our use case is that the package name for Windows needs to be different than any other platform and so indeed, I will try to use a parameter. Thank you both!