Hello hello. For the devs developing using Macs. Are you able to compile your compose app to the Int...

# compose-desktop

[Leandro Borges Ferreira]

Hello hello. For the devs developing using Macs. Are you able to compile your compose app to the Intel version of Macs (x86-64)? I'm using arm based and I can only build for this archtecture using ./gradlew packageReleaseDmg. Does anyone also have this problem?

[ephemient]

https://kotlinlang.slack.com/archives/C3PQML5NU/p1736617113390069?thread_ts=1736616643.869389&cid=C3PQML5NU

[Leandro Borges Ferreira]

That's gold! Thanks man!

[Leandro Borges Ferreira]

Oh sorry, thanks pink spider!

[ephemient]

it's a https://en.wikipedia.org/wiki/Tachikoma and don't worry about it blob wink

[mikehearn]

You can also cross-build from any-to-any platform using Conveyor (https://hydraulic.dev/)

[Leandro Borges Ferreira]

Very nice product! Thanks letting me know and good job on this one! I'll check it out carefully

[Rok Oblak]

I just use github actions. For example, to create the MSI for Windows:

name: Build and Package MSI

on:
  push:
    tags:
      - buildDesktopBundles

jobs:
  build:
    runs-on: windows-latest

    steps:
      - uses: actions/checkout@v4

      - name: Set up JDK 17
        uses: actions/setup-java@v2
        with:
          java-version: '17'
          distribution: 'adopt'

      - name: Create local.properties file
        run: |
          echo "STORE_PASS=${{ secrets.STORE_PASS }}" > local.properties
          echo "KEY_PASS=${{ secrets.KEY_PASS }}" >> local.properties
        shell: bash

      - name: Create secrets.txt file
        run: |
          echo "SENTRY_AUTH_TOKEN_FRONTEND=${{ secrets.SENTRY_AUTH_TOKEN_FRONTEND }}" > secrets.txt
          echo "SENTRY_AUTH_TOKEN_BACKEND=${{ secrets.SENTRY_AUTH_TOKEN_BACKEND }}" >> secrets.txt
        shell: bash

      - name: Build and package MSI
        run: .\gradlew packageReleaseMsi

      - name: Find MSI file
        id: findmsi
        run: |
          $msiPath = Get-ChildItem -Path desktopBuilds\main-release\msi\*.msi | Select-Object -ExpandProperty FullName
          echo "MSI_PATH=$msiPath" | Out-File -FilePath $env:GITHUB_ENV -Append
        shell: powershell

      - name: Debug MSI_PATH
        run: | 
          echo "MSI_PATH is set to: ${{ env.MSI_PATH }}"
        shell: bash

      - name: Upload MSI as Artifact
        uses: actions/upload-artifact@v4
        with:
          name: app-MSI
          path: ${{ env.MSI_PATH }}

[Leandro Borges Ferreira]

Thanks for sharing @Rok Oblak. I'm still not deploying my app as a Windows application, but when I do I'll take a deeper look into this

[Rok Oblak]

What I meant to say, is you can use the same to deploy for any architecture, just use the right machine (github offers a mac machine for free for some minutes per month) and the right command, i.e. in my case for windows it was packageReleaseMsi

[Leandro Borges Ferreira]

yep yep, I get it. I just need check how my app runs in a windows machine once so I can start to deploying it in windows.