corelyzer for linux? #2
Comments
|
Hello Ilya,
First off, I'm sorry it took me so long to respond to your message. Corelyzer is one of many applications I'm working on, and I was distracted by other tasks the last few weeks.
Unfortunately, the presentation you referenced is quite old, and predates my involvement with the CoreWall suite of software. I believe there was a time when we had Linux builds up and running as we do for Windows and Mac, but due to immediate needs and a lack of Linux users such as yourself, I'm sad to say I can't speak to the state of Corelyzer on Linux. I've never actually seen the software built for, or running on, any Linux distribution. I can't dedicate significant time to this at the moment, but if you're interested in trying to get it up and running, I'll help where I can. I'd love to have functional Linux builds again!
In corelyzer/app, there's a build.gradle file listing dependencies for the Corelyzer application. The first dependency is on the internal 'scenegraph' project, so I think it's best to start there. Adapt the Mac OS X instructions in corelyzer/scenegraph/README and see if you get anywhere. I assume wget and gsed are already included in your Linux distro, so you can probably skip Step 1. You'll probably need to make some tweaks to the 'build-jni-mac' Gradle task in corelyzer/scenegraph/build.gradle to complete a build.
Sorry I can't be of more direct help right now! Good luck! Keep me posted on your project and I'll offer suggestions if I can.Thanks,brian On Wednesday, April 5, 2017 4:55 AM, Ilja Kocken <[email protected]> wrote:
Hi! I'm trying to build corelyzer on my 4.10.6-1-ARCH linux machine from the source code, but I see no list of required dependencies. (on this presentation it lists the app as cross-platform)After running sh gradlew clean package I get the following error:Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
FAILURE: Build failed with an exception.
* Where:
Build file '/home/japhir/Downloads/corelyzer-2.0.4_rc4/corelyzer-2.0.4_rc4/app/build.gradle' line: 14
* What went wrong:
A problem occurred evaluating project ':app'.
Cause: You must specify a urls for a Maven repo.
* Try:
Run with -s or -d option to get more details. Run with -S option to get the full (very verbose) stacktrace.
BUILD FAILED
Total time: 1.826 secs
I look forward to hearing from you! :-)—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hi Brian, Ilja, I tried as well on Linux and came to as far as Ilja did. The problem seems to be of a more general nature and affect everybody who tries to build Corelyzer for the first time, independent of architecture. According to my understanding, gradle looks for the Maven SDK and, if not present, tries to download it from the repositories that are specified in app/build.gradle lines 12-16. The repos on line 14 were deprecated many years ago. In one forum it was mentioned that http://download.java.net/maven/2/ was replaced by https://maven.java.net/content/groups/public/ (though I don't know whether this is correct or not). And https://maven.atlassian.com/maven1/maven2 was shut down 5 years ago (c.f. https://www.atlassian.com/blog/archives/shutting-down-maven-1-repositories-on-maven-atlassian-com), apparently without replacement. It seems like the only reasonable option is to move to a more recent Maven SDK. Unfortunately, I have no clue how to proceed with this. Henning |
|
In your app/build.gradle line 14 Change this url to urls, then it will go on. Tested on Windows with 32 bit java 7 sdk |
|
Welp, it's been a few years, but I've finally got Corelyzer building and running on Linux...specifically, on a clean install of Clone the repo, checkout the I am far from a seasoned Linux user, so there are caveats. Most notably, it only works on a clean install of 18.04.4. Do not update the kernel from the provided 5.3.0-28-generic to 5.4+! Otherwise Corelyzer will crash at launch. For some reason, JOGL and libEGL.so don't play well together with kernel 5.4+. My notes on this can be found in scenegraph/linux_build_breadcrumb.txt. Perhaps one of you savvy Linux users can shed some light on this issue? If so, please reply here, and send a pull request if you have a fix! It would also be great to have a pre-built Corelyzer for Linux so folks don't have to build from scratch. I have no experience in packaging Linux applications, so any help would be much appreciated. Hope this is enough to get people started...let me know how it goes! |
|
I tried to build it on my distro with all the newest packages, but as expected this fails because it relies on some old syntax. |
|
I could try to run it on an Ubuntu 18.0 VM because I already have that up and running for another software package that doesn't rely on the latest versions of its dependencies. Might take me some time to get around to it though. I have some experience creating Arch User Repository packages for my distribution, but none for Ubuntu, unfortunately, so I can't help you there. |
|
@japhir : The linux_build branch works fine when the development environment is set up correctly. Check your jdk. The "Deprecated Gradle features ..." warning will remain but apparently doesn't matter (I haven't checked this further). For sorghumking, corelyzer worked on a VM with Ubuntu 18.04 LTS but crashed on a VM with 20.04 LTS. I have no problems with 20.04 LTS on a physical machine (Intel i915 graphic driver). This needs further confirmation/testing, but is most likely an issue with the mesa graphic driver on the VM + JOGL + the 5.4 kernel of 20.04 LTS. So try to avoid either the mesa graphic driver (you probably can't on a VM) or kernel 5.4/20.04 LTS. |
|
@daoane I'm not on Ubuntu but on Arch Linux, a rolling release Linux distro, which means that all the packages I use are the latest versions that are available. Therefore on my local machine I can't choose to use a specific older version of certain libraries. Oh and yeah, I'm using the latest mesa/vulkan (20.1.8) drivers. So I guess in this case it's probably easiest to try it on my Ubuntu VM |
|
I think my comment above is based on a wrong conclusion. Mesa is present on all systems, the difference is the driver for the (physical /virtual) graphic card. Which might be the issue for Ubuntu 20.04 LTS VM (works on physical machine). I think only more testing will help. |
|
I figured out I hadn't installed the Arch equivalent of the output from the terminal after building scenegraph |
|
I had the jni.h problem as well and it was due to the different java versions that I had installed (both openjdk and Oracle). I reinstalled openjdk-11 and the problem was solved. Maybe build.gradle needs to be adapted to ArchLinux (just a guess). |
|
Indeed, the
As @daoane mentioned, you'll need to adapt these paths in the |
|
I'm happy to report that Corelyzer launches successfully on a non-VM Ubuntu 18.04.4 with Linux kernel 5.4.0-48-generic. More good news: Corelyzer launches successfully in both Ubuntu 18.04.4 and 20.04.1 virtual machines (Parallels 15) if hardware acceleration is disabled. In the VM settings, choose Graphics, Advanced Settings, and turn 3D Acceleration to "Off". |
|
Great that you're testing it on Linux as well! I've just reinstalled |
Hi! I'm trying to build corelyzer on my 4.10.6-1-ARCH linux machine from the source code, but I see no list of required dependencies. (on this presentation it lists the app as cross-platform)
After running
sh gradlew clean packageI get the following error:I look forward to hearing from you! :-)
The text was updated successfully, but these errors were encountered: