Closed codedump closed 1 year ago
CS-Studio is not supported for JDK18 You need to use jdk8 or jdk11
Just for the record: Is JDK8 really still supported? Does the JDK need to be 64 bit, or is JDK 8 on 32 bit still supported?
I guess I should have only mentioned jdk11. I am using jdk11, I have not tested with jdk8 in awhile now. I think ITER might be still using it with jdk8.
Even with jdk11 I remember some issues associated with missing/deprecated modules.
@codedump we would recommend using https://github.com/ControlSystemStudio/phoebus/ if you can
CS-Studio is not supported for JDK18 You need to use jdk8 or jdk11
@shroffk, may I suggest documenting this? ;-) Or maybe it's already documented but I couldn't find it (?).
I came through the website, downloaded the package didn't find any README or hint on the download site itself, and had a look at what I assume is closest to the documentation's "installation" section.
I agree... for the time being I added a blurb on the readme. https://github.com/ControlSystemStudio/cs-studio/pull/2718
Have you considered moving to Phoebus
If you're just starting to look at this, didn't even get it to run, you'll definitely be better off starting with https://github.com/ControlSystemStudio/phoebus/ which no longer requires Eclipse, builds faster, and runs with JDK 11-18
@shroffk @kasemir Thank you for pointing me towards Phoebus, I'll definitely have a look at it! :-)
I didn't (still don't) know the difference between Phoebus and CS-Studio. I was about to evaluate tooling around EPICS, starting with CS-Studio, when I hit the problem I described. Meanwhile I was also nudged towards Phoebus by people at BESSY (Berlin), so I'll definitely have a closer look at it.
I'm also thinking about adaptations of tooling from other areas (e.g. Prometheus monitoring and Grafana) for EPICS dashboarding, although this is a one-way communication only -- just monitoring, no controlling. But the advantage is that the user and developer base is huge. If one would write e.g. a Prometheus exporter for EPICS, one would instantly gain access to a really vast, well-documented infrastructure. But of course, one would leave behind the goodies that CS-Studio / Phoebus has to offer that go beyond monitoring...
CS-Studio was first built on Eclipse to use its SWT graphics, preference system, plugin .. and built system. Eventually compiling CSS took 45 minutes, if it built at all.
So we started to look for alternatives and found JavaFX as a new graphics lib, plain Java preferences as very similar to the Eclipse preferences, plain Java SPI as very similar to Eclipse (sorry: OSGi) plugins, and we can use maven or ant to build. So "phoebus" has now pretty much all the functionality, it is the "current" version of CS-Studio, builds in 5..10 minutes. It's where new stuff is added (PVAccess on IPv6, alarm system that runs with Kafka instead of RDB+JMS, ..)
Hello,
I'm attempting to start cs-studio on a fresh Fedora Silverblue toolbox (think of it as of a newly installed Fedora Linux system). Essentially, the steps I do after download and unpacking are these:
It crashes and leaves behind the following log file contents in
~/.cs-studio/.metadata/.log
:What is going wrong?
Thanks & Cheers, F.