@here please tell me what is the path where msi an...
# compose-desktop
k
@here please tell me what is the path where msi and deb is generated when we execute ./gradlew packageDeb and ./gradlew packageMsi like for ./gradlew packageDeb we have path like desktopApp/build/compose/binaries/main/dmg/file.dmg
c
Doesn't directly answer your question but please don't try to
@here
in a channel with over 2500 people in it
k
Ig here doesn't work, didn't notify people ig. If yes then noted
c
Even if it did work, notifying that many people is incredibly disruptive
To your question, is there any console output when you run
packageMsi
?
k
Sorry, noted down
So I'm using mac and it didn't generate msi and deb
So, that way I asked
c
Hmm, can you actually compile for targets other than the one you're running on? I know for a fact you can only run
packageDmg
on a Mac. Don't know if that's true for deb/msi
k
We can run that g command but output isn't generated
c
Have you tried looking through the
build/
folder to find it? Or maybe used the
find
command in your shell?
eg:
find desktopApp/build
to list out the files in the directory tree
Documentation here is pretty clear, actually:
After a build, output binaries can be found in
${project.buildDir}/compose/binaries
.
And even more conclusively:
package<FormatName>
(e.g.
packageDmg
or
packageMsi
) are used for packaging the app into the corresponding format. Note, that there is no cross-compilation support available at the moment, so the formats can only be built using the specific OS (e.g. to build
.dmg
you have to use macOS). Tasks that are not compatible with the current OS are skipped by default.
"there is no cross-compilation support"
❤️ 1
k
Yaa actually, thanks for clarity. I'll use github action to generate that
👍 1
c
You will need to run
packageDeb
on a linux machine for it to work,
packageMsi
on windows, etc
k
Yes exactly
m
There's also https://hydraulic.dev/ which can cross-build Compose Desktop packages, along with other features.
k
@mikehearn any tutorial how to use it
c
m