This is just a thought, but perhaps you could include other developer applications as static libraries. The advantages will be that other developers would not have to give away their sources, you would not encounter any code related to the identification of the code and the problems associated with it, including the static libraries are completely safe.
The only drawback is that developers will still have to deliver the content separately, and they need to learn how to create a static library. The entry point for each application / each library will also require, maybe even a small interface, to allow a container application to find out about the status of individual applications, cancel them, etc.
As I said, this is just an idea, there may be problems with this approach that I donโt see right now. But maybe others can comment on this ...
You might want to check out this link to learn a little about creating static object libraries c.
source share