release includes libuv.a

[JeffBezanson]

The windows binary install includes lib\julia\libuv.a. I assume this is not necessary? There is also a bin\libuv-11.dll which I believe is also unnecessary since we statically link libuv.

[nalimilan]

Actually we have the same problem with Linux packages, where I'm removing the file manually. AFAICT there's no need for libuv once the build process is done. Or would applications embedding Julia need it?

[tknopp]

No it is included in libjulia

[tkelman]

We can probably get rid of both. I've personally been using the static libuv.a out of the Windows binary to save the time of building libuv in from-scratch builds (on AppVeyor and locally), but would be okay with handling this differently at the nightly-packaging level. A separate deps-dist target for all the static and shared libs posted to a separate download would work well for this purpose. I could write the Makefile rule if others agree with the idea (particularly @ihnorton since he's the one who set up the Windows nightlies).

[JeffBezanson]

cc @staticfloat
bump

[staticfloat]

@vtjnash in de88a2e you added in installation of libuv.a and include files. Just double-checking with you that it's okay to remove them.

[vtjnash]

These files were needed to build the JuliaWebRepl package (unmaintained) against the current Julia version. I don't know if anyone is using them, but they can probably be removed.

Applications that embed Julia would probably be interested in the uv.h headers, but they probably should be installed in a private include folder (such as lib/julia)

[tkelman]

libuv.a is not in the binaries any more, so this can probably be closed. But since #8024 we also aren't installing uv.h, which breaks the embedding use case since julia.h include's it. There are some uv_ types in julia.h, so do we need to put the libuv header back?