It is possible to create a `pkg` for intel mac, on a m1 mac ?

# compose-desktop

[Raphael TEYSSANDIER]

It is possible to create a pkg for intel mac, on a m1 mac ?

[Alexander Maryanovsky]

Only with virtualization

[Alexander Maryanovsky]

Not sure that even exists, though. Not a very common use-case probably.

[Raphael TEYSSANDIER]

Because I want to publish an app on AppStore, but it tells me that I need to support Intel Mac. Since we can’t make an universal binary. I’m kind of stuck

[Alexander Maryanovsky]

Yeah, it’s a problem.

[Alexander Maryanovsky]

Unfortunately it’s a limitation of jpackage that we can’t really much about.

[Raphael TEYSSANDIER]

So, only way right now it’s to have a intel mac to make binaries ?

[Alexander Maryanovsky]

Yes

[Raphael TEYSSANDIER]

Ok, thank’s for answering

[Michael Paus]

We had this question (vor DMG instead of PKGs) just a few days ago and it was concluded that it should be possible to make an Intel build on ARM hardware by just utilizing Rosetta 2. See: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1696348252391969

[Raphael TEYSSANDIER]

Thank’s, gonna try

[Raphael TEYSSANDIER]

Do I need to make a packageReleaseDmg or can I just use packageDmg ?

[Raphael TEYSSANDIER]

We can release an dmg on test flight?

[Michael Paus]

I don’t know the App Store rules, but with the above concept it should also be possible to build PKGs and it would be interesting to know whether you could confirm that. I can’t because I don’t own an ARM mac yet.

[Raphael TEYSSANDIER]

I did release a pkg with success. But now I stuck with CODESIGNING 1 Taskgated Invalid Signature

[Stefan Oltmann]

Yes. The current GitHub runners are primarily Intel-based, which is not an issue for me at the moment because Intel architecture is universally compatible. However, considering that I work on an M1-based system, I anticipate potential challenges in the future if GitHub shifts away from Intel architecture.