IMHO, GAPI_STANDALONE name should not be used to switch between static/shared builds.

Alternatives:

• allow to define GAPI_EXPORTS externally and wrap all current stuff under (#ifndef GAPI_EXPORTS. Add -DGAPI_EXPORTS for static builds
• introduce separate flag to control statis/shared (CMake usually adds _EXPORTS variant of this flag - see DEFINE_SYMBOL CVAPI_EXPORTS property)

I believe GAPI_STANDALONE is more about building G-API independently of OpenCV (and as of now the static library is produced)

I see your point about GAPI_EXPORTS but it seems like this will be an additional compile definition just for the sake of the GAPI_EXPORTS which I doubt anyone (besides us) would update anyway.

Not sure I understand the version with CVAPI_EXPORTS that you propose, from the code it looks like that the difference is only in CMake's function to be used but the actual behavior/logic is the same, am I wrong?

CMake's DEFINE_SYMBOL documentation is here.

@rgarnov @alalek I simplified: looks like we don't need non-OpenCV part altogether, please look again

Meanwhile, if now we're making a change which is then will be 180*-reverted, y we do need to do it at all?

Maybe @andrey-golubev and @rgarnov go to IE folks and discuss moving IE's "fluid" to a separate .SO? :)

@dmatveev from my discussion with @rgarnov it seems like it's easier to do it this way right now and then see what's a proper way. good point about commenting out and not deleting, will do this

@andrey-golubev ok!

@dmatveev @alalek updated

Thanks!