Closed jerboaa closed 7 months ago
@jerboaa why not add svm-foreign.jar to
Mx.artifacts
and let the "Copy jars" step in line 112 take care of it as it does for the rest?
Good point. Do you know which artefact coordinates I need to use?
Good point. Do you know which artefact coordinates I need to use?
I'd say org.graalvm.nativeimage:svm-foreign.jar
, but it shouldn't really matter as we are not publishing it as a maven artifact, i.e. the coordinates won't be used except in a potential error message if the jar file is not found.
Good point. Do you know which artefact coordinates I need to use?
I'd say
org.graalvm.nativeimage:svm-foreign.jar
, but it shouldn't really matter as we are not publishing it as a maven artifact, i.e. the coordinates won't be used except in a potential error message if the jar file is not found.
OK
@zakkak Done now. Please have another look.
The copying for
svm-foreign.jar
inmaster
is broken it copied the directorysubstratevm/mxbuild/dists/jdk23
to file$MANDREL_HOME/lib/svm/svm-preview/svm-foreign.jar
which is broken for two reasons:lib/svm/builder/svm-preview
over JDK 22+ location next tosvm.jar
inlib/svm/builder
directory.This patch fixes this and also copies the corresponding
src.zip
which we do for other artefacts as well.Thoughts?