Processing build does not work on Linux #1043
Comments
|
To investigate this I also referred back to my previously created fork of the processing repo: https://github.com/hx2A/processing4 I know the build worked before. But today, when I run it, I get this message: $ ./gradlew build
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.11/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
> Task :core:different:compileDifferentSharedLibraryDifferentObjc FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':core:different:compileDifferentSharedLibraryDifferentObjc'.
> Error while evaluating property 'compilerVersion' of task ':core:different:compileDifferentSharedLibraryDifferentObjc'.
> Cannot invoke "org.gradle.nativeplatform.toolchain.internal.gcc.metadata.GccMetadata.getVendor()" because the return value of "org.gradle.platform.base.internal.toolchain.SearchResult.getComponent()" is null
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 3s
5 actionable tasks: 1 executed, 4 up-to-dateIt fails on the ThinkDifferent code. I know I made some PRs related to this in the past. I did that work on my MacOS computer though. I also remember we removed the compiled objective c code from the repo, and that we had a good reason for it, but did that also make it impossible for non MacOS users to run the build? The build should work on all machines. That's the only way we can ever fix platform specific bugs. |
|
Hey Jim! Are you compiling with any JDK version other than 17 x64? Any version higher than 17 or an arm version would kill the process at this stage (will be fixed by #957) Some more info, I've seen this before and it is a really annoying issue as it fails and gives improper errors. The failure actually happens within the legacy Ant step used by the Preprocessor but Gradle will report it as if somewhere else. |
|
I will try to finish my work on #957 tomorrow morning, as you're not the first to run into this issue |
|
Hi @Stefterv ! I downgraded to Java 17 and then everything worked correctly. Does this build contain the necessary MacOS thinkdifferent native libraries? What I'm trying to achieve here is to run the py5 build. The py5 build process is dependent on the Processing. Previously I would download one of the release archives (e.g. processing-4.3.4-linux-arm64.tgz) and unzip that, but as of 4.4.0, files like that are no longer being created. I need to adapt py5's build process to either use the result of the Gradle build or use one of the portable files. I have a lot of questions about how to best adapt py5 to the new Processing build process. Rather than ask those questions here, I created an issue for this in the py5 repo. @Stefterv , can you have a look and help me figure this out? |
|
And I am going to close this because Java 17 fixed this and it seems you are already aware of the issue. |
I am attempting to run the build on a Linux computer but the Gradle daemon is getting killed. I can run it just fine on my MacOS machine. I seem to remember I was able to run the build on Linux in the past, with Gradle, so there must be a change from the past few months that caused this to stop working on Linux.
Here is the output from the terminal:
When I use the suggest
--infooption I see the task that fails is:app:includeCore:I did do Google searches for Gradle daemons getting killed and it seems this is not an uncommon problem for Linux users. I did create a
gradle.propertiesfile:I can't disable the daemon though. It always says
To honour the JVM settings for this build a single-use Daemon process will be forked. How do I get rid of the daemon? None of the fixes I read about via Google worked for me. How can I get the build to work on Linux?The text was updated successfully, but these errors were encountered: