Closed stelfrich closed 5 years ago
@imagejan Do you have a Windows 7 machine that you could build/test this PR on? I only have a 32bit Windows 10 that I could use to compile the launcher, but not a Windows 7 one to properly test it...
I wanted to take the opportunity to set up a running gcc
on my Windows system, but when running mvn
, I get:
and in the target
folder, I end up with imagej-launcher-5.0.1-SNAPSHOT-amd64-Windows-gcc-executable.nar
which apparently isn't the right thing for my platform, is it?
@stelfrich if you can provide me with a compiled launcher executable, I'm happy to test it on a Windows 7 system.
Maybe the easiest thing would be to merge this, wait for the AppVeyor build and use that? And then revert if there is any regression noticed?
Maybe the easiest thing would be to merge this, wait for the AppVeyor build and use that? And then revert if there is any regression noticed?
Let's do this. Shouldn't break anything...
I downloaded imagej-launcher-5.0.1-20180821.152133-36-win64.exe
and put it into my existing Fiji installation on Windows 7.
This is what I noticed:
the new launcher doesn't seem to pick up my system Java: when trying to launch, it complains:
The program can't start because jvm.dll is missing from your computer.
But after a short while (without splash screen), the ImageJ window comes up, reporting Java 10.0.1
(Note that the previous launcher imagej-launcher-5.0.0-20171212.062926-36-win64.exe
in the same Fiji installation runs fine with Java 1.8.0_172 and displaying a Fiji splash screen.)
when renaming the java-old
directory in my installation back to java
, both launchers start up with splash screen and Java 1.8.0_66
when I do File > New > Script..., then Language > Python, then Run, I still get:
console: Failed to install '': java.nio.charset.UnsupportedCharsetException: cp0.
in all situations tested... :cry:
I downloaded imagej-launcher-5.0.1-20180821.152133-36-win64.exe and put it into my existing Fiji installation on Windows 7.
That version that you mention here, @imagejan, is one that does not have the PR included yet (according to its timestamp at least). Would you mind checking again with imagej-launcher-5.0.1-20180925.115628-44-win64.exe
?
the new launcher doesn't seem to pick up my system Java: when trying to launch, it complains
Let's try (although it might not be possible because property handling might have issues when falling back to the system java
executable for launching) to focus on the Python issue. If this persists, let's open another issue to investigate this.
does not have the PR included yet (according to its timestamp at least)
sorry for that: I was getting the SNAPSHOT from maven.imagej.net, but didn't double-check the timestamp...
Would you mind checking again with imagej-launcher-5.0.1-20180925.115628-44-win64.exe?
Yup, with this one I don't get the error message any more. I tried with Java 10.0.1 (after that spurious jvm.dll error dialog mentioned above) and with the bundled Java 1.8.0_66, it's fine in both cases.
Thanks again, @stelfrich!
Did anyone try setting this flag on the Java side using System.setProperty
instead of in the native code?
Fixes #56.