I found https://softwareengineering.stackexchange.com/questions/110380/call-gpl-software-from-non-gpl-software that directs to https://www.gnu.org/licenses/gpl-faq.html#MereAggregation
Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged).
If the modules are included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.
By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.
As I understand it, in general I can call a GPLed program with any software, without violating GPL license.
Though in some cases where one program would be effectively created ("if the semantics of the communication are intimate enough...") then it would not count as starting a separate program.