I am writing a closed-source Java Card applet. But as a part of the functionality, I call a static RIPEMD160 method licenced under AGPL. The static method can be compiled separately and loaded onto the Java Card as a library. I can then use the
.exp file from the compiled library, in order to call this compiled library function within my applet. The
.exp file provides the information about the interface of whatever just got compiled. Name of the function, where in memory it lives, etc.
Could I distribute the AGPL-licenced function library and my applet under different licences alongside each other, so that my applet code remains closed source? Or would the fact that I'm calling the function from an interface of an AGPL piece of code force my code to also be GPL-compatible?
I have an intuition that I can keep my applet code closed source because what I'm doing is akin to system calls. So technically all software that is written for Linux and makes use of Linux system calls should be open-source now? I don't think that's true.
But I could be missing something here.