Avoid thin archives

Describe the bug After updating to 0.60.0 I started seeing some errors when linking against static archives linked by meson 0.60.0 error adding symbols: malformed archive Comparing the ninja files between 0.59.3 and 0.60.0 show the only difference is a T option added to the LINK_ARGS and the resulting static archive is very small. Is there a way of avoiding this behaviour? I understand when you’re building a static archive to then use immediately in the same project you might want a thin archive but if I just want to build a normal static archive there doesn’t seem to be a way to do so. Also shouldn’t the new behaviour be opt in rather than the default? I can imagine this might break quite a few existing meson scripts.

[eli-schwartz]

It should be noted that apparently thin archives do not play nicely with nvcc (the CUDA compiler) when passing static libraries to a custom target, the use case of which has prompted someone to submit a PR adding a thin: <bool> keyword to force disable it.

I still think hooking up the install layer (and automatically using it in the conan recipe) is a bit nicer / more idiomatic, plus it works everywhere, including the 0.60.0 release.

[nathanaelg]

Yup seems perfectly reasonable, just not something I was aware of because it did just work until this point! I will add the installation stuff in any projects which are outputting libraries.