Re: [incubation] wrap binaries into a plugin

["Alois Z." <alois.zoitl@xxxxxx>]

Hi,
 
I just noticed that the webmail client destroyed my response. So here again with better formating:
 
 
thanks for the further clarification. So in short I'll start with the CQs and see where it leads me to.
 

> Gesendet: Mittwoch, 29. Juni 2016 um 09:41 Uhr
> Von: "Jens Reimann" <jens.reimann@xxxxxxxxxxxxxxx>
> An: incubation@xxxxxxxxxxx
> Betreff: Re: [incubation] wrap binaries into a plugin

> Hello Alois,

> not completely right. You will need CQs, but "works with", "pre-requiste" or "pre-requiste exempt".  The PMC will need to discuss/vote on the request with the outcome of either of those and in the case or > "pre-requisite" EMO has to approve as well. For a "pre-requisite" also a full IP check will be made.

> The main difference between "works with" and "pre-requiste" is the question if the solution can do "its thing" without that dependency or not. Of course the question is what is that your application does. > That is why there has to be a discussion around that to find it out.
 
Will be interesting how this is sorted out for our operating system problem. Here I still don't know for which I'll need to file a CQ.

> Now as far as I remember 4DIAC, there is a modular build system which uses CMAKE and some options to enable/disable things from the build. So you could run a Linux build, all problematic things excluded and distribute this as a binary without problems. Then you could offer a source release, allowing the user to enable things in the build, looks to me like a works-with then. Because your core runtime still works without those dependencies. Still you would need that "works with CQ", since you will be using their API in your source code.
 
Yes this is exactly as it is for 4diac FORTE. Per default all additional dependencies are even disabled and a user has to explicitly enable them.

> The third option would be to extend your build system in a way that your download the source release of 4DIAC and allow the user to add its own source package, recompile and have him add his own dependencies, but in a project-standardized way.
 
This is also something we already have as a typicall user will need to add his own FBs and maybe libraries when he ports 4diac FORTE to a new system or uses it on a already supported system.
 
Alois