我正在使用
官方文档()指出,要构建 .dmg
和 .msi
可执行文件,我们至少需要 jdk 15 。
我能够构建 .dmg
安装程序并将其安装在MacOS上。
但是该应用程序不会打开,也没有显示错误消息(打开应用程序时什么都没发生),
所以我的问题是:
- 运行此应用程序需要哪些最小JDK版本?
- 我们是否需要在运行此应用程序的机器上安装JDK15或更高版本?
- 运行桌面构成乘数应用程序的其他最小软件 /硬件要求是什么?
注意:我正在发布这些查询,因为没有关于以下主题的官方文件:
运行桌面构成乘数应用程序的最低软件要求。
I am developing an app with Desktop Compose Multi-Platform.
It will run on both Mac OS and Windows OS.
The official document(Document Link) states that, in order to build .dmg
and .msi
executable we need at least JDK 15.
I was able to build a .dmg
installer and installed it on MacOS.
But the app does not open and no error message is shown (nothing happens on opening the app)
So my questions are:
- What minimum JDK version will be required to run this app?
- Do we need to JDK15 or higher installed on the machine that will run this app ?
- What are other minimum software / hardware requirements for running a Desktop Compose Multiplatform app ?
Note: I am posting these queries as there is no official document around the following topic:
Minimum software requirements for running Desktop Compose Multiplatform App.
发布评论
评论(1)
在将JPackage与我的桌面组合应用程序一起创建
.dmg
可执行文件之前,我遇到了这个问题。据我所知,问题不应该在您安装的JDK版本中。就我而言,该应用程序会显示已安装,但是当我单击它时,它将尝试运行,然后立即关闭而不会显示任何UI。问题最终是我试图让父母
流程ID
在Mac上没有专门工作。如果您不尝试在您的情况下访问任何系统信息/过程',则另一种可能性是某种权限问题,因此您可以尝试使用
sudo
的终端运行它。最后要尝试的是进行“手动调试”。在应用程序的开头创建文件,并在整个过程中添加写线以准确地缩小应用程序崩溃的位置。
I've ran into this issue before using JPackage with my desktop compose app to create a
.dmg
executable. As far as I know, the issue shouldn't be in the JDK version you have installed. In my case, the app would show up installed, but when I clicked it, it would try to run and then close immediately without showing any UI.The problem ended up being that I was trying to get the parents
process ID
which didn't work specifically on mac.If you aren't trying to access any system info/process' in your case, the other possibility is some sort of permissions issue so you could try running it from terminal with
sudo
.The final thing to try is doing a "manual debug". Creating a file in the start of the app and adding write lines throughout to narrow down exactly where the app is crashing.