CUDACPP is installed even if MadGraph version is not officially supported

[Qubitol]

By chance, I tried installing CUDACPP through install cudacpp inside MadGraph v3.6.4 (which as of today is not officially supported, see the version info file.
I also tested one process and it works...

Is it supposed to install it anyway? No warning/error was displayed during the operation.
I would at the very least print a warning, given there may be incompatibilities.

On the contrary, on v3.5.11 the installation doesn't even start, and it fails as expected.

[roiser]

Which version is picked? A warning would be good to show.

When you say "it works" would this fix #1043 ?

[Qubitol]

It picks the latest one v1.00.02.

I meant I tried just a simple process (g g > t t~) to see if there were major incompatibilities but it was working fine.
However, I just tried the process mentioned in #1043

$./bin/mg5_aMC
$generate p p > t t~ t t~ j
$output madevent_simd
$launch

and indeed it fails with the same issue.

[valassi]

Ciao Daniele, I was having a look to understand Olivier's comment about colors in my MR #1049.
If I upgrade to the version tagged as 3.6.4 (in developer mode, not with an install cudacpp, but I guess it is the same), I do get a warning

> Plugin MG5aMC_PLUGIN.CUDACPP_OUTPUT has marked as NOT being validated with this version: 3.6.4. 
> It has been validated for the last time with version: 3.6.3

Hope this helps. Andrea

[Qubitol]

I see, the warning is displayed only when using CUDACPP features, while nothing is displayed while doing install cudacpp.

Should we throw a warning also during installation?

[valassi]

Ah I see your point. I think this is a general feature of the plugin system however, not of cudacpp? I imagine one can add a version validation also during the install phase, sounds like a good idea.