Reason to alway to build both static and shared libs

[Jianshen Liu]

Hi all,

Could I know the reason for always building both static and shared libs of
DPDK? I can find the patch
<https://www.mail-archive.com/dev@dpdk.org/msg83487.html> to enable this
behavior, but it seems that it didn't mention the reason behind it. Also,
if I propose a change to use "both" as the default for default_library in
meson's config file and still allow users to choose either static or shared
as they want, is there any reason against that change?

Thanks,
Jianshen