Remove static libraries from static builds

[ericonr]

Motivated by commit ioc: remove static libraries from non-static builds. from #19

If an IOC uses the support library build configuration, where there is a support library which is the one that's actually linked to the support modules, it's possible that generates a static support library as well (though I'm not 100% sure, it would be good to confirm it), and that would take up room in the image, even though it can't be used.

[henriquesimoes]

Let me see if I really understand it. In such hypothetical scenario, the static support library will be produced and live in /opt/$REPONAME because it is specified to be compiled by the IOC build itself. Therefore, make clean won't remove it (as it is indeed one of multiple final binaries), and it will be finally copied along with the whole IOC tree to the final image, even though its code has already been compiled into the IOC program (in bin). Am I right?

That's a tricky case where I'd like there was something the build system could do to help us. Something that means "install only runtime artifacts, skipping development ones." But I'm afraid there is not, and there won't be.

[ericonr]

and it will be finally copied along with the whole IOC tree to the final image, even though its code has already been compiled into the IOC program (in bin). Am I right?

I had originally thought of the case where the support library is linked dynamically, but that indeed shouldn't happen with STATIC_BUILD=YES. So indeed, the code should already be in the final executable, but there might be leftover .a (and possibly .so) files. I will check an IOC that uses this format.