I want to write a closed-source desktop application that uses a piece of GPL software in the background.I know that I can't link to a GPL library (libgit.a).  But if I embed a GPL application (git.exe) into a closed source application, unzip the GPL app to a temporary location, and then make calls to it using some form of IPC (e.g. command line arguments), is that legal?non-GPL application calls a GPL application at the command line -> definitely legalnon-GPL application links to a GPL application using function calls -> definitely illegalnon-GPL application bundles, distributes, and calls a GPL application at the command line -> ?Distributing a GPL application and making silent IPC calls is functionally identical to linking, as far as the end-user is concerned.  Does GPL care about whether I'm linking inside of one process, or using IPC to do the linking?  It seems like closed source applications like GitHub's desktop clients do this, but maybe I'm misunderstanding how they work.NOTE: This is different than the other GPL questions on this site, because it asks about embedding a GPL application, not linking to a library in the traditional sense.  The answers have been specific to this case and very helpful to me.NOTE2: Mods found a new duplicate, and this time they are right - it is actually asking the same question as this (although the details are a little more jumbled).  The best answer has been modded into oblivion though.  Key points are copied here:VMWare Server's example shows that it's okay to include the object code into your distribution andinstall it alongside your programpack it into a compound file within its footage if it's clearly a compound file and can be taken apart with widely available tools (an ISO image)
Can I distribute a GPL executable (not a library) in a closed-source application?
licensing;gpl;linking