Foivos Zakkak

Hi @gilles-duboscq this is a kind reminder :)

> Maybe we should start from the beginning: what are you trying to achieve? I have assumed so far that you just want to build the jars of a suite...

> OK, i see. But what is the purpose of --no-native? Internally we build the Java bits separately from the native bits. > I suppose you are trying to work...

> @olpaw, do you think the Truffle & NFI support could be split out to a separate jar? @olpaw doing so would allow us to stop ["patching" the suite files...

@olpaw could you also please have a look at this? (the discussion mostly, not necessarily the PR itself)

The issue of fetching `LIBFFI_SOURCES` is actually no longer an issue, so sorry if the outdated discussion misled you. The current issue is that despite using: ``` mx --primary-suite-path substratevm...

For branches it should be as easy as: ```diff diff --git a/mx.py b/mx.py index a69e55e..d876123 100755 --- a/mx.py +++ b/mx.py @@ -6298,7 +6298,7 @@ class GitConfig(VC): cmd += ['--no-checkout', '--shared',...

@fniephaus you may use `MX_GIT_CACHE` as well to speedup your CI pipelines. ``` MX_GIT_CACHE Use a cache for git objects during clones. * Setting it to `reference` will clone repositories...

@fniephaus yes if caching is not possible on your CI setup, then `MX_GIT_CACHE` doesn't make sense. For Maxine we are using Jenkins and docker agents. To make sure we don't...

> @boris-spas I know that TravisCI supports caching...but like I said before, build performance is unlikely to improve because of it. It's only useful when caching stuff that takes some...