by Hooray » Mon Feb 21, 2022 2:46 pm
You should probably reach out to the software folks you are working with, i.e. developers/software engineers or programmers and "coders", the point being - this may all sound pretty fancy and sophisticated, but someone with the corresponding background can certainly help you understand what the FSF/(L)GPL expect you to do when you're using an (L)GPL'ed program.
Also, S&J's comments are unfortunately not being helpful either, since they're at best incomplete and depend highly on the given context.
So you really need to get someone involved familiar with the coding side of things and with the corresponding legalese.
The bottom line being, if you are going to use certain open source software with closed-source/proprietary software, you're becoming subject to the terms of that license, which is why it's best to avoid that scenario in a proprietary/commercial project. Basically, you could also search the forum/wiki for "unity" specifically and you will see that this has been previously done, but it all depends highly on your use-case/context, it could be a no-brainer or it can open a huge can of -legal- worms.
Without further context, the best advice at this point is to look up the definition of so called "tight coupling" and interfacing at "arm's length" - at that point, you will understand that using a separate open source binary with an interfacing mechanism (network, sockets, IPC etc) will isolate you from all legal troubles, unless you happen to be subect to the Affero GPL.
Again, all this can be done in a safe and legal way, but you need to have people involved who know what they're doing - and there's nothing scandalous about it either.